smells like a bug :) -- dims
On 11/17/05, Burbach, Matthias <[EMAIL PROTECTED]> wrote: > I will do so, but it'll take some time. > > Does this mean it is a true bug and not a new concept? > > Regards, > Matthias > > -----Ursprüngliche Nachricht----- > Von: Davanum Srinivas [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 16. November 2005 19:05 > An: [email protected] > Betreff: Re: wsdl2java does not generate Java types for simple WSDL types > anymore > > > Matthias, > > Could i trouble you to create a bug report and upload your WSDL? and the soap > traces? > > thanks, > dims > > On 11/16/05, Burbach, Matthias <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I observed that in contrast to Axis 1.1 wsdl2java does no longer > > generate Java classes for simple WSDL types in Axis 1.2 and above > > anymore. > > > > For example, my WSDL contains the following type definition: > > > > <xs:simpleType name="anrede"> > > <xs:restriction base="xs:int"> > > <xs:minInclusive value="0"> > > </xs:minInclusive> > > <xs:maxInclusive value="2"> > > </xs:maxInclusive> > > </xs:restriction> > > </xs:simpleType> > > > > wsdl2java of Axis 1.1 generated a Java class Anrede.java from this > > bit. Axis 1.1 XML requests referencing this type look as follows > > (extraction): > > <anrede xsi:type="n1:anrede">0</anrede> > > > > wsdl2java of Axis 1.2, however does **not** generated a Java class > > Anrede.java from this bit. Axis 1.2 XML requests, on the contrary, > > referencing this type look as follows (extraction): > > <anrede xsi:type="xsd:int">0</anrede> > > > > This difference causes the server I sent such requests to to reject > > requests of the latter kind:-( > > > > Consequently, I seem to face a serious interoperability problem due to > > the upgrade from Axis 1.1 to Axis 1.2. The problem remains when using > > Axis 1.2.1 or Axis 1.3. > > > > > > Can anybody tell me why this is so and what one is to supposed to do > > about it?? > > > > Regards, > > Matthias > > > > P.S.: I found several reports on this type of problem in the > > newsgroups but none proposed a solution:-(( > > > > > -- > Davanum Srinivas : http://wso2.com/blogs/ > > -- Davanum Srinivas : http://wso2.com/blogs/
