-
1. Re: JBOSSWS creates WSDL incompatible with JDK Endpoint class and .Net Clients
ritenru Jun 8, 2010 9:14 AM (in response to ritenru)<warning type="editorial">
Well, this is a first. Three weeks without a single comment (even one to tell me I shouldn't do it this way).
</warning>
I installed the jboss-6.0.0-20100429-M3 version with no change in behavior.
Upon further investigation, I discovered that the message part name attribute (//message/part[@name]) is different between the Endpoint RI and the JBOSS generated WSDL. If I modify the WSDL from JBOSS by changing the name="..." to name="parameters", the .NET client works fine.
{code}
/cygdrive/c/foo/jbossws/mod-wsdl> diff cfg.wsdl cfg.wsdl.orig
118c118
< <part element="tns:createConfigEntry" name="parameters"/>
---
> <part element="tns:createConfigEntry" name="createConfigEntry"/>
121c121
< <part element="tns:listEntriesResponse" name="parameters"/>
---
> <part element="tns:listEntriesResponse" name="listEntriesResponse"/>
127c127
< <part element="tns:listEntries" name="parameters"/>
---
> <part element="tns:listEntries" name="listEntries"/>
130c130
< <part element="tns:createConfigEntryResponse" name="parameters"/>
---
> <part element="tns:createConfigEntryResponse" name="createConfigEntryResponse"/>
133c133
< <part element="tns:getConfigValue" name="parameters"/>
---
> <part element="tns:getConfigValue" name="getConfigValue"/>
139c139
< <part element="tns:deleteConfigEntryByName" name="parameters"/>
---
> <part element="tns:deleteConfigEntryByName" name="deleteConfigEntryByName"/>
145c145
< <part element="tns:deleteConfigEntryByNameResponse" name="parameters"/>
---
> <part element="tns:deleteConfigEntryByNameResponse" name="deleteConfigEntryByNameResponse"/>
154c154
< <part element="tns:getConfigValueResponse" name="parameters"/>
---
> <part element="tns:getConfigValueResponse" name="getConfigValueResponse"/>{code}