[
https://issues.apache.org/jira/browse/AXIS2-4353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Amila Chinthaka Suriarachchi updated AXIS2-4353:
------------------------------------------------
Priority: Major (was: Blocker)
removing the priority as suggested by the last comment.
For the moment you can create the axis2 service your own and use it. then
correct fix should go to DefaultURIResolver.
> ServiceClient can not resolve WSDL with imported schemas
> --------------------------------------------------------
>
> Key: AXIS2-4353
> URL: https://issues.apache.org/jira/browse/AXIS2-4353
> Project: Axis2
> Issue Type: Bug
> Components: client-api
> Affects Versions: 1.4.1, 1.4
> Environment: all
> Reporter: Ben Reif
> Assignee: Amila Chinthaka Suriarachchi
> Fix For: 1.6
>
> Attachments: ResolveXSDTestCase.zip
>
>
> I am using the ServiceClient to invoke a Web Service, but the WSDL file and
> imported schema files are located within a jar file that is in the Classpth.
> I can get the Definition object, and I set the DocumentBaseURI to the proper
> URL pointing inside the jar file, but when I pass it to the ServiceClient I
> get an error saying that it can't resolve the imported schema files. This
> happens when it calls AxisService.createClientSideAxisService().
> It looks like a fix was put in the WSDLToAxisServiceBuilder class (the
> addition of the setCustomResolver() method) so that you can set a custom
> URIResolver to resolve imported schema files. This gets inherited by the
> WSDL11ToAxisServiceBuilder, however the problem is that this setter is not
> exposed to the ServiceClient, so I can never use it. The ServiceClient
> constructors and the AxisService.createClientSideAxisService() methods should
> take in an additional argument so that calling code can pass in the right
> URIResolver instance which would get set on the WSDL11ToAxisServiceBuilder
> instance.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
