[ 
https://issues.apache.org/jira/browse/TUSCANY-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526627
 ] 

Simon Laws commented on TUSCANY-1684:
-------------------------------------

The incompatibility of the namespaces, i.e. the extra xsd on the end, is due to 
the Axis21.2 library we are using. This is not generated by Axis2 1.3 I need to 
fin out when we are going to move to 1.3 and, depending on the answer, 
potentially patch up the generated WSDL in some way. 

> Web Service binding incompatibility when referencing a WebService hosted on 
> JBoss
> ---------------------------------------------------------------------------------
>
>                 Key: TUSCANY-1684
>                 URL: https://issues.apache.org/jira/browse/TUSCANY-1684
>             Project: Tuscany
>          Issue Type: Bug
>          Components: Java SCA Axis Binding Extension
>    Affects Versions: Java-SCA-0.99
>         Environment: Windows XP, Tuscany 0.99 downloaded the 10th Sept. 2007, 
> JBoss-5.0.0.Beta2
>            Reporter: Marco Dalcó
>         Attachments: ReferenceToJBOSSWSTestCase.zip
>
>
> Deploy a simple WebService on JBoss. Access it using a tool like SoapUI. It 
> works fine. Access it from Tuscany, with a <reference> containing <binding.ws 
> uri="http://theUri";>. It fails.
> Comparing the messages they send, there are two main differences:
>  
> 1) The namespace of the method invoked. In the Tuscany message it has an 
> additional "xsd" at the end
> 2) The name of the parameter of the method. It is "arg0" with SoapUI and 
> "param0" with Tuscany
>  
> It could be a problem of library versions, WebService specifications, a bug 
> or whatever.
> I tried the "requires", "wsdli:wsdlLocation", "wsdlElement" in many 
> combinations, with no success.
> What is this incompatibility due to?

-- 
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]

Reply via email to