12:25
PM
To: [EMAIL PROTECTED]
Subject: RE: Attribute's corrupted
with WSDL2Java
I
can't disagree with you. All I can say is that JAX-RPC dictates this and we
must follow JAX-RPC. The potential for name clashes is a big failing. Perhaps
this will be addressed if anyone works on a JAX-R
]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: RE: Attribute's corrupted with WSDL2Java
Also what if we have a WSDL definition as follows:
< element name="CREATEBY" nillable="true"
2002 10:41
AM
To: '[EMAIL PROTECTED]'
Subject: RE: Attribute's corrupted
with WSDL2Java
I understand what you are
say, but this is not a very robust conversion. The biggest problem with
this is that the WSDL file used in this example was generated from Java source,
and the java so
: Re: Attribute's corrupted
with WSDL2Java
This
isn't a bug. This is what JAX-RPC specifies. It tries to convert XML names to
Java conventional names. One of the rules is, remove each underscore and force
the following character to upper case.
Note that this ONLY affects the Java mapp
l XML name.
Russell Butek
[EMAIL PROTECTED]
Please respond to [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
cc:
Subject: Attribute's corrupted with WSDL2Java
Any class that has attributes that have underscores in it are not generated
Any class that has attributes that have underscores in it
are not generated correctly, i.e. the underscores are removed!
Example WSDL (minus unrelated structures):
Java code generated by WSDL2Java (minus unrelated
code)
