.appendSuper( super.hashCode() )
.append( this.value )
.toHashCode();
}
}
> -Original Message-
> From: Bouche Paul [mailto:[EMAIL PROTECTED]
> Sent: Monday, February 28, 2005 12:41 PM
> To: axis-user@ws.apache.org
> Subject: RE: Using axis ant ta
he.org
> Subject: Re: Using axis ant task with typed enums
>
>
> Ulrich,
>
> First of all, WSDL does not contain any "class" descriptions. WSDL
> contains element and type descriptions -- specified using XML Schema.
> If you read through the archives, you will see
nal Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Montag, 28. Februar 2005 16:41
> To: axis-user@ws.apache.org
> Subject: Re: Using axis ant task with typed enums
>
>
> Ulrich,
>
> First of all, WSDL does not contain any "class"
obj) { ... }
public int hashCode() { ... }
}
> -Original Message-
> From: Anne Thomas Manes [mailto:[EMAIL PROTECTED]
> Sent: Montag, 28. Februar 2005 16:41
> To: axis-user@ws.apache.org
> Subject: Re: Using axis ant task with typed enums
>
>
> Ulrich,
>
&g
Ulrich,
First of all, WSDL does not contain any "class" descriptions. WSDL
contains element and type descriptions -- specified using XML Schema.
If you read through the archives, you will see frequent
recommendations to take a "WSDL first" or "Schema first" approach to
web services rather than a "
Hi,
in the meantime I came to the conclusion, that my question has no solution that
could satisfy me. I fear that there is no way to create a WSDL file containing
a class description, where the class contains just public static members (or
does the WSDL spec offer a way to express such things?)
