[ http://issues.apache.org/jira/browse/AXIS2-1889?page=comments#action_12459916 ] James Shiell commented on AXIS2-1889: -------------------------------------
This can be relatively simply solved by changing DeploymentEngine.populateService to call wsdl2AxisServiceBuilder.setCustomWSLD4JResolver() and wsdl2AxisServiceBuilder.setCustomResolver(). A simple (and somewhat naive) implementation of each is attached. As an aside, it would be quite nice to be able to set resolvers as a user, without having to subclass. > WSDL with relative imports fails with FileNotFoundException. > ------------------------------------------------------------ > > Key: AXIS2-1889 > URL: http://issues.apache.org/jira/browse/AXIS2-1889 > Project: Apache Axis 2.0 (Axis2) > Issue Type: Bug > Components: wsdl > Affects Versions: 1.1 > Environment: WLS 9.2, J2SE 1.5.0.4, Windows XP SP2 > Reporter: James Shiell > Attachments: sample.java > > > When using a pre-defined WSDL with relative imports the imports are not > resolved. This appears to be because WSDLReader is always passed an empty > base URI in WSDL11ToAxisServiceBuilder.readInTheWSDLFile(..). > e.g. > META-INF/service.wsdl > META-INF/service.xsd > If the import references "service.xsd" then the file is not found. > I would expect it to be picked up from the same location. I would presume > this could be accomplished by setting the base URI of the > WSDLToAxisServiceBuilder in the DeploymentEngine.popualteService(..) method. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
