You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2007/07/18 12:15:04 UTC
[jira] Commented: (AXIS2-1889) WSDL with relative imports fails
with FileNotFoundException.
[ https://issues.apache.org/jira/browse/AXIS2-1889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12513520 ]
Deepal Jayasinghe commented on AXIS2-1889:
------------------------------------------
I think WSDL URI issues is fixed in Axis2 1.3-RC1 please download that and see.
> WSDL with relative imports fails with FileNotFoundException.
> ------------------------------------------------------------
>
> Key: AXIS2-1889
> URL: https://issues.apache.org/jira/browse/AXIS2-1889
> Project: 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
> Assignee: Eran Chinthaka
> Priority: Critical
> Fix For: 1.3
>
> Attachments: sample-j2se14.java, sample.java, wsdl.zip
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org