[#5886] - Bad WSDL for PermissionsManagementService

Posted by tomreilly on August 29, 2012 - 6:35pm
Category:
Bug report
 Priority:
High
 Status:
New
Project:
JasperReports® Server
 Severity:
Block
 Resolution:
Open
Component: Reproducibility:
Always
 Assigned to:
mgeise
Subscribe

<p>Trying to get a web reference for a C# web service application in Visual Studio 2010. On original addition of the web reference, of when I do a subsequent "update web reference", I get the following error: Custom tool error: Unable to import WebService/Schema. Unable to import binding 'PermissionsManagementServiceSoapBinding' from namespace 'http://www.jasperforge.org/jasperserver/ws'. Unable to import operation 'getPermissionsForObject'. Please review type declaration 'WSObjectPermission' from namespace 'http://www.jasperforge.org/jasperserver/ws': element 'permissionRecipient' does not specify a type. And sure enough, the element "permissionRecipient" defines attributes "name" and "nillable", but not attribute "type"</p>

tomreilly's picture
tomreilly
2
Joined: Aug 29 2012 - 1:07pm
Last seen: 10 years 7 months ago

5 Comments:

#1Posted by mgeise on September 10, 2012 - 5:53pm

I have added this to our internal bug tracking system - 20326

#2Posted by giulio on September 11, 2012 - 10:53am

To get the web service schema, you should connect to this url:

http://yourserver:8080/jasperserver/services/repository?wsdl

a valid user name of JasperReports Server is required to access the url

Giulio

#3Posted by tomreilly on September 12, 2012 - 1:45pm

Giulio,

I think we are still working to get to agreement on the nature of the problem. Please consider the following - I hope it makes my issue clearer.

You directed me to the repository service, which is working fine for us. That locally installed URL is:

http://theshiznit.tricast.com:8080/jasperserver/services/repository?wsdl

I am trying to work with the permissions service. For us, the locally installed target is:

http://theshiznit.tricast.com:8080/jasperserver/services/PermissionsMana...

When I go to this URL, I see the WSDL XML for the Jasper Server permissions service, which includes the following:

<complexType name="WSObjectPermission">
<sequence>
<element name="uri" type="xsd:string"/>
<element name="permissionRecipient" nillable="true"/>
<element name="permissionMask" type="xsd:int"/>
</sequence>
</complexType>

The element "permissionRecipient" has no "type" attribute. The Visual Studio web server reference utilities require it, as does the standalone wsdl.exe utility. Am I doing a better job of explaining the problem?

Thank you,

Tom

#4Posted by tomreilly on November 6, 2012 - 11:35am

Please consider this problem report again, and see if you can spare the time to fix it for us. Thank you!

#5Posted by sri.vedantham on May 15, 2013 - 8:56am

Is this issue fixed yet?

We need it urgently

Feedback
randomness