You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by melix <ce...@lingway.com> on 2007/11/09 14:33:41 UTC
Enumeration problem
Hi,
Using CXF 2.0.2, I have a problem using CXF with a service which throws an
exception which contains an enumeration field. The WSDL is generated
correctly, and I use wsdl2java for generating client stubs. The WSDL shows
the following :
<xs:simpleType name="fultyExceptionType">
<xs:restriction base="xs:string">
<xs:enumeration value="LILIAN_CONNECTION_FAILURE"/>
<xs:enumeration value="INTERNAL_ERROR"/>
<xs:enumeration value="IO_ERROR"/>
<xs:enumeration value="UNKNOWN_CREATION_TEMPLATE"/>
<xs:enumeration value="MISSING_PARAMETER"/>
<xs:enumeration value="UNKNOWN_APPLICATION"/>
<xs:enumeration value="QUERY_PARSE_ERROR"/>
<xs:enumeration value="APPLICATION_ALREADY_EXISTS"/>
<xs:enumeration value="INDEXATION_SESSION_NOT_ENDED"/>
<xs:enumeration value="UNHANDLED_EXCEPTION"/>
<xs:enumeration value="JDBC_CONNECTION_FAILURE"/>
</xs:restriction>
</xs:simpleType>
<xs:complexType final="#all" name="fultyExceptionTypeArray">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="item"
nillable="true" type="tns:fultyExceptionType"/>
</xs:sequence>
</xs:complexType>
The stubs also seem to be generated correctly, and FultyExceptionTypeArray
class is also generated. But at runtime, it fails with the following error :
Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1 counts
of IllegalAnnotationExceptions
Two classes have the same XML type name
"{mycompany.com}fultyExceptionTypeArray". Use @XmlType.name and
@XmlType.namespace to assign different names to them.
this problem is related to the following location:
at com.mycompany.ws.FultyExceptionType[]
this problem is related to the following location:
at com.mycompany.ws.FultyExceptionTypeArray
There seems to be a conflict with the "Array". Can't figure out what's
happening...
--
View this message in context: http://www.nabble.com/Enumeration-problem-tf4777694.html#a13667022
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Enumeration problem
Posted by melix <ce...@lingway.com>.
Two solutions, either :
- move to CXF 2.0.3 which fixes the problem (easy)
- edit the stubs to change the namespace
Cedric
Mon wrote:
>
> Hi!
> I'm seeing the same issue. Any ideas how to get round it?
> Thanks,
> Monica
>
>
> melix wrote:
>>
>> Hi,
>>
>> Using CXF 2.0.2, I have a problem using CXF with a service which throws
>> an exception which contains an enumeration field. The WSDL is generated
>> correctly, and I use wsdl2java for generating client stubs. The WSDL
>> shows the following :
>>
>> <xs:simpleType name="fultyExceptionType">
>> <xs:restriction base="xs:string">
>> <xs:enumeration value="LILIAN_CONNECTION_FAILURE"/>
>> <xs:enumeration value="INTERNAL_ERROR"/>
>> <xs:enumeration value="IO_ERROR"/>
>> <xs:enumeration value="UNKNOWN_CREATION_TEMPLATE"/>
>> <xs:enumeration value="MISSING_PARAMETER"/>
>> <xs:enumeration value="UNKNOWN_APPLICATION"/>
>> <xs:enumeration value="QUERY_PARSE_ERROR"/>
>> <xs:enumeration value="APPLICATION_ALREADY_EXISTS"/>
>> <xs:enumeration value="INDEXATION_SESSION_NOT_ENDED"/>
>> <xs:enumeration value="UNHANDLED_EXCEPTION"/>
>> <xs:enumeration value="JDBC_CONNECTION_FAILURE"/>
>> </xs:restriction>
>> </xs:simpleType>
>> <xs:complexType final="#all" name="fultyExceptionTypeArray">
>> <xs:sequence>
>> <xs:element maxOccurs="unbounded" minOccurs="0" name="item"
>> nillable="true" type="tns:fultyExceptionType"/>
>> </xs:sequence>
>> </xs:complexType>
>>
>> The stubs also seem to be generated correctly, and
>> FultyExceptionTypeArray class is also generated. But at runtime, it fails
>> with the following error :
>>
>> Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1
>> counts of IllegalAnnotationExceptions
>> Two classes have the same XML type name
>> "{mycompany.com}fultyExceptionTypeArray". Use @XmlType.name and
>> @XmlType.namespace to assign different names to them.
>> this problem is related to the following location:
>> at com.mycompany.ws.FultyExceptionType[]
>> this problem is related to the following location:
>> at com.mycompany.ws.FultyExceptionTypeArray
>>
>> There seems to be a conflict with the "Array". Can't figure out what's
>> happening...
>>
>>
>
>
--
View this message in context: http://www.nabble.com/Enumeration-problem-tp13667022p14597629.html
Sent from the cxf-user mailing list archive at Nabble.com.
Re: Enumeration problem
Posted by Mon <mo...@gmail.com>.
Hi!
I'm seeing the same issue. Any ideas how to get round it?
Thanks,
Monica
melix wrote:
>
> Hi,
>
> Using CXF 2.0.2, I have a problem using CXF with a service which throws an
> exception which contains an enumeration field. The WSDL is generated
> correctly, and I use wsdl2java for generating client stubs. The WSDL shows
> the following :
>
> <xs:simpleType name="fultyExceptionType">
> <xs:restriction base="xs:string">
> <xs:enumeration value="LILIAN_CONNECTION_FAILURE"/>
> <xs:enumeration value="INTERNAL_ERROR"/>
> <xs:enumeration value="IO_ERROR"/>
> <xs:enumeration value="UNKNOWN_CREATION_TEMPLATE"/>
> <xs:enumeration value="MISSING_PARAMETER"/>
> <xs:enumeration value="UNKNOWN_APPLICATION"/>
> <xs:enumeration value="QUERY_PARSE_ERROR"/>
> <xs:enumeration value="APPLICATION_ALREADY_EXISTS"/>
> <xs:enumeration value="INDEXATION_SESSION_NOT_ENDED"/>
> <xs:enumeration value="UNHANDLED_EXCEPTION"/>
> <xs:enumeration value="JDBC_CONNECTION_FAILURE"/>
> </xs:restriction>
> </xs:simpleType>
> <xs:complexType final="#all" name="fultyExceptionTypeArray">
> <xs:sequence>
> <xs:element maxOccurs="unbounded" minOccurs="0" name="item"
> nillable="true" type="tns:fultyExceptionType"/>
> </xs:sequence>
> </xs:complexType>
>
> The stubs also seem to be generated correctly, and FultyExceptionTypeArray
> class is also generated. But at runtime, it fails with the following error
> :
>
> Caused by: com.sun.xml.bind.v2.runtime.IllegalAnnotationsException: 1
> counts of IllegalAnnotationExceptions
> Two classes have the same XML type name
> "{mycompany.com}fultyExceptionTypeArray". Use @XmlType.name and
> @XmlType.namespace to assign different names to them.
> this problem is related to the following location:
> at com.mycompany.ws.FultyExceptionType[]
> this problem is related to the following location:
> at com.mycompany.ws.FultyExceptionTypeArray
>
> There seems to be a conflict with the "Array". Can't figure out what's
> happening...
>
>
--
View this message in context: http://www.nabble.com/Enumeration-problem-tp13667022p14597625.html
Sent from the cxf-user mailing list archive at Nabble.com.