[
https://issues.apache.org/jira/browse/TUSCANY-1684?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12526652
]
gengshaoguang commented on TUSCANY-1684:
----------------------------------------
I tried something here: as to reference a jboss WS from Tuscany side.
It fails because of:
1. wsdl2 java generation does not support namespace like "http://a.b.c/d"; slash
here in. So a fishy promotion is to change the provider into "http://a.b.c";.
2. Tuscany's transformer transforms input object into OMElement with it's name
as a "param0.." of the wsdl's element. But JBoss accept only input named to
ELEMENT NAME.
If wsdl is:
<complexType name="X">
<sequence>
<element name="person" nillable="true" type="string"/>
<element name="product" nillable="true" type="string"/>
</sequence>
</complexType>
soap difference will be:
<soap:Body>
<param0></param0>
<param1></param1>
</soap:Body>
vs.
<soap:Body>
<person></person>
<product></product>
</soap:Body>
> 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]
