[Apologies to anyone who has seen this before - it didn't seem to get
through to the list forst time.]
I have a doc/literal web service, WSDL generated from .NET. My WSDL
defines various types, for example:
<s:element name="getUserDetails">
<s:complexType>
<s:sequence>
<s:element minOccurs="0" maxOccurs="1" name="userId" type="s:string" />
</s:sequence>
</s:complexType>
</s:element>
When I generate Java from the WSDL using WSDL2Java from Axis 1.1 final
this maps to a Java class called '_getUserDetails'. From a quick look
over the JAX-RPC spec (and from my understanding of these matters)
this is not a legal name for a Java class (at least in standards
terms). I've tried building and running with the lastest Axis source
drop (13 Aug) and get the same behaviour.
Has anyone else seen this sort of class name generation? Is it a bug?
Could it be caused by a naming clash - I also have an operation called
'getUserDetails' definied in my WSDL (note that this is not
hand-written WSDL - it's just what .NET gave me). Also, if I generate
Java from this WSDL using the version of Axis (1.0) embedded in
JBuilder 8 (either using JBuilder UI or running WSDL2Java from the
command-line) this maps to a Java class called 'GetUserDetails' -
which seems more reasonable.
Matt.
--
/\/\att Stupple -- +44 20 7542 9554 -- [EMAIL PROTECTED]
--------------------------------------------------------------- -
Visit our Internet site at http://www.reuters.com
Get closer to the financial markets with Reuters Messaging - for more
information and to register, visit http://www.reuters.com/messaging
Any views expressed in this message are those of the individual
sender, except where the sender specifically states them to be
the views of Reuters Ltd.
