You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Simon Laws (JIRA)" <tu...@ws.apache.org> on 2008/02/14 10:07:08 UTC
[jira] Commented: (TUSCANY-2043) documentBaseURI is null when
multiple wsdls in contribution with same namespace
[ https://issues.apache.org/jira/browse/TUSCANY-2043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12568837#action_12568837 ]
Simon Laws commented on TUSCANY-2043:
-------------------------------------
Hi
I took your WSDL files and made a sample. I see an effect just by running it that you don't mention....
Caused by: org.apache.tuscany.sca.interfacedef.wsdl.impl.InvalidWSDLException: Element cannot be resolved: {http://helloworld/xsd}getGreetings
at org.apache.tuscany.sca.interfacedef.wsdl.impl.WSDLOperationIntrospectorImpl$WSDLPart.<init>(WSDLOperationIntrospectorImpl.java:272)
This is during the resolution of the WSDL. I'm curious that the affect for you is just a null documentBaseURI rather than the error I see. It maybe that I set the test up slightly differently (Can you post the java source files also for comparison? I only see the class files in the attached jar)
Anyhow something is definitely going wrong with the way that the runtime tries to aggregate types found in the same namespace. Am debugging now so I'll post again when I know more.
Simon
> 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-Next
>
> 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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org