Hi Chris, I am afraid that this would be a particularly hard thing to fix. I would be afraid of breaking existing users if we changed this. Sorry that we picked the wrong name!
I would still file a bug in JIRA on this, if you haven't already. -- Tom Jordahl Macromedia Server Development > -----Original Message----- > From: Chris Berry [mailto:[EMAIL PROTECTED] > Sent: Friday, May 13, 2005 11:27 AM > To: [email protected] > Subject: typeDesc > > Greetings, > I am processing the following XSD with WSDL2Java and get a name > conflict for typeDesc in the generated Java. I am working around this > by hacking the generated Java, but obviously that is a problematic > workaround. > > Seems that Axis might use a somewhat less likely variable name in the > generated code (say _typeDesc or axisTypeDesc) ?? BTW; it is difficult > for me to change the code on our side since this variable is part of a > very widely used C-struct. > > Is there any chance that this might get "fixed" in the future? > Thanks, > -- Chris > > <xsd:complexType name="Product_t"> > <xsd:sequence> > <xsd:element name="Id" type="ProductId_t" codegen:cname="id" /> > ....... snip ..... > <xsd:element name="TypeDesc" codegen:cname="type_desc"> > <xsd:simpleType> > <xsd:restriction base="xsd:string"> > <xsd:maxLength value="254" /> > </xsd:restriction> > </xsd:simpleType> > </xsd:element> > </xsd:complexType>
