[
https://issues.apache.org/jira/browse/TUSCANY-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Simon Laws resolved TUSCANY-2043.
---------------------------------
Resolution: Fixed
I have put some changes in to solve the immediate issue. In particular the XSD
aggregation now maintains all original XSD and the WSDL determination algorithm
in the Axis2 providers now operates correctly when recursing into the
aggregated types. I have raised
http://issues.apache.org/jira/browse/TUSCANY-2045 to track the subsequent
proposal for a more targeted approach to WSDL/XSD artifact resolution.
> documentBaseURI is null when multiple wsdls in contribution with same
> namespace
> ----------------------------------------------------------------------------------
>
> Key: TUSCANY-2043
> URL: https://issues.apache.org/jira/browse/TUSCANY-2043
> Project: Tuscany
> Issue Type: Bug
> Reporter: Lou Amodeo
> Assignee: Simon Laws
> Fix For: Java-SCA-1.2
>
> Attachments: helloworld-ws-asynch.jar
>
>
> I have a case where there are 2 wsdl files in the contribution with the same
> namespace. After the WSDL resolution the
> documentBaseURI attribute of the wsdl's DefinitionImpl is null. The is
> normally completed in the WebServiceBindingProcessor.resolve(). In this
> particular case there are 2 binding.ws elements in the contribution. One for
> the service and one for its <callback> binding. If I change the TNS of one
> of the WSDL files then the documnetBaseURI is filled in during the
> WebServiceBindingProcessor.resolve. So it appears there is in issue in the
> WSDL Model resolver when it finds multiple WSDL files with the same TNS.
>
--
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]
