Hi Aleck,
Use -H when you generate your javabean to have Axis' getTypeDesc method
generated into a helper class. I suppose that would prevent the clash (I
have never tried, though).
Axis should have used a more 'reserved' name like __typeDesc, but they
didn't. Fortunately the work-around is simple.
Regards,
Dies
Alick Buckley wrote:
Hi Guys,
If a WSDL complex type element name is typeDesc, it will conflict with the
internal Axis generated typeDesc variable and the bean code cannot compile.
The other internal variable use a double underscrore prefix.
<complexType name="Employee">
<sequence>
<element name="AGE" nillable="true" type="xsd:string"/>
<element name="first_name" nillable="true" type="xsd:string"/>
<element name="id" nillable="true" type="xsd:string"/>
<element name="name" nillable="true" type="xsd:string"/>
<element name="newHome10Years" nillable="true" type="xsd:string"/>
<element name="newHouse10years" type="xsd:int"/>
<element name="typeDesc" nillable="true" type="xsd:string"/>
<===================
</sequence>
</complexType>
/**
* Sets the typeDesc value for this Employee.
*
* @param typeDesc
*/
public void setTypeDesc(java.lang.String typeDesc) {
this.typeDesc = typeDesc;
}
private java.lang.Object __equalsCalc = null;
public synchronized boolean equals(java.lang.Object obj) {
private boolean __hashCodeCalc = false;
public synchronized int hashCode() {
private static org.apache.axis.description.TypeDesc typeDesc =
public static org.apache.axis.description.TypeDesc getTypeDesc() {
regards
Alick Buckley
LANSA Research and Development
LANSA Pty Ltd
Phone: +61289070243
http://www.lansa.com
mailto:[EMAIL PROTECTED]
