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)" <de...@tuscany.apache.org> on 2011/08/11 12:35:27 UTC

[jira] [Created] (TUSCANY-3918) Split WSDL files in the same namespace casues problems for ws binding

Split WSDL files in the same namespace casues problems for ws binding
---------------------------------------------------------------------

                 Key: TUSCANY-3918
                 URL: https://issues.apache.org/jira/browse/TUSCANY-3918
             Project: Tuscany
          Issue Type: Bug
          Components: SCA Java Runtime
    Affects Versions: Java-SCA-2.0
         Environment: All
            Reporter: Simon Laws
             Fix For: Java-SCA-2.0


I have the following scenario:

<wsdl:definitions targetNamespace="http://serialize"
                  xmlns:tns="http://serialize"
                  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
                  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	              name="serialize-top">

    <wsdl:import namespace="http://serialize" location="wsdl-serialize-nested.wsdl" />

    <wsdl:binding name="AccountSoapBinding" type="nested:Account">
...


<wsdl:definitions targetNamespace="http://serialize"
                  xmlns:tns="http://serialize"
                  xmlns:account="http://accounts"
                  xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
                  xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
                  xmlns:xsd="http://www.w3.org/2001/XMLSchema"
	              name="questionmark-import-nested">

    <wsdl:types>
...

<composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912"
			xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200912"
			targetNamespace="http://www.tuscany.apache.org/tests/binding/ws/axis2"
           name="WSDLSerialize">

    <component name="AccountService">
		<implementation.java class="org.apache.tuscany.sca.binding.ws.axis2.AccountService"/>
		<service name="Account">
	        <binding.ws uri="http://localhost:8085/services/AccountService" 
	                    wsdlElement="http://serialize#wsdl.binding(AccountSoapBinding)"/>
	    </service>
    </component>

</composite>

This causes the ws binding to fail with an NPE in Axis when it's trying to find the AccountSoapBinding binding. I'm guessing that having both WSDL documents in the same namespace is causing confusion somewhere. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] [Commented] (TUSCANY-3918) Split WSDL files in the same namespace casues problems for ws binding

Posted by "Scott Kurz (JIRA)" <de...@tuscany.apache.org>.
    [ https://issues.apache.org/jira/browse/TUSCANY-3918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13083125#comment-13083125 ] 

Scott Kurz commented on TUSCANY-3918:
-------------------------------------

Just curious when this is failing... could you paste the stack trace?
Thx,Scott

> Split WSDL files in the same namespace casues problems for ws binding
> ---------------------------------------------------------------------
>
>                 Key: TUSCANY-3918
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-3918
>             Project: Tuscany
>          Issue Type: Bug
>          Components: SCA Java Runtime
>    Affects Versions: Java-SCA-2.0
>         Environment: All
>            Reporter: Simon Laws
>             Fix For: Java-SCA-2.0
>
>
> I have the following scenario:
> <wsdl:definitions targetNamespace="http://serialize"
>                   xmlns:tns="http://serialize"
>                   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>                   xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>                   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> 	              name="serialize-top">
>     <wsdl:import namespace="http://serialize" location="wsdl-serialize-nested.wsdl" />
>     <wsdl:binding name="AccountSoapBinding" type="nested:Account">
> ...
> <wsdl:definitions targetNamespace="http://serialize"
>                   xmlns:tns="http://serialize"
>                   xmlns:account="http://accounts"
>                   xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
>                   xmlns:wsdlsoap="http://schemas.xmlsoap.org/wsdl/soap/"
>                   xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> 	              name="questionmark-import-nested">
>     <wsdl:types>
> ...
> <composite xmlns="http://docs.oasis-open.org/ns/opencsa/sca/200912"
> 			xmlns:sca="http://docs.oasis-open.org/ns/opencsa/sca/200912"
> 			targetNamespace="http://www.tuscany.apache.org/tests/binding/ws/axis2"
>            name="WSDLSerialize">
>     <component name="AccountService">
> 		<implementation.java class="org.apache.tuscany.sca.binding.ws.axis2.AccountService"/>
> 		<service name="Account">
> 	        <binding.ws uri="http://localhost:8085/services/AccountService" 
> 	                    wsdlElement="http://serialize#wsdl.binding(AccountSoapBinding)"/>
> 	    </service>
>     </component>
> </composite>
> This causes the ws binding to fail with an NPE in Axis when it's trying to find the AccountSoapBinding binding. I'm guessing that having both WSDL documents in the same namespace is causing confusion somewhere. 

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira