yes, i know that there is no validation. but my web services need to mantain all informations, including that restriction... so i suppose that axis isn't compliant with jax-rpc.
> -----Messaggio originale----- > Da: Gurkan, Ozzie (MAN-Corporate) [mailto:[EMAIL PROTECTED] > Inviato: luned́ 15 dicembre 2003 21.21 > A: '[EMAIL PROTECTED]' > Oggetto: RE: Axis Bug? > > > Remove the restriction bit, since there is no validation anyways... > > -----Original Message----- > From: Tevoi Andrea [mailto:[EMAIL PROTECTED] > Sent: Monday, December 15, 2003 3:22 AM > To: [EMAIL PROTECTED] > Subject: Axis Bug? > > > Hi all, > I've seen that for a simple type derived from another simple > type WSDL2Java > tool generates a wrapped class, not according with jax-rpc > specs (4.2.5). > > example: > > <xsd:complexType name="MyBean"> > <xsd:sequence> > ... > <xsd:element name="StringRestriction"> > <xsd:simpleType> > <xsd:restriction base="xsd:string"> > <xsd:maxLength value="4"/> > </xsd:restriction> > </xsd:simpleType> > </xsd:element> > ... > </xsd:sequence> > </xsd:complexType> > > For the Element (that derives from xsd:string) inside the ComplexType, > WSDL2java generates a StringRestriction.java class, not according with > jax-rpc specifications (4.2.5). Moreover, MyBean.java class > has a method > setStringRestriction(StringRestriction stringRestriction) > > is this an Axis bug? > > thanks in advance, > Andrea Tevoi >
