axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Amila Chinthaka Suriarachchi (JIRA)" <>
Subject [jira] Commented: (AXIS2-3556) Cannot use JAXBRI data binding with the version service WSDL
Date Fri, 29 Feb 2008 15:20:51 GMT


Amila Chinthaka Suriarachchi commented on AXIS2-3556:

This is a problem with the jaxbri. it does not allow to keep an Element and a Complex type
with the same name. I compiled the following schema with xjc tool comes with the jaxbri.
<xs:schema attributeFormDefault="qualified"
    <xs:complexType name="Exception">
            <xs:element minOccurs="0" name="Exception" nillable="true" type="xs:anyType"/>
    <xs:element name="Exception">
                <xs:element minOccurs="0" name="Exception" nillable="true" type="ns:Exception"/>
    <xs:element name="getVersionResponse">
                <xs:element minOccurs="0" name="return" nillable="true" type="xs:string"/>

it gave the same exception.
But when I rename the Element Exception to ExceptionE it worked correctly.

> Cannot use JAXBRI data binding with the version service WSDL
> ------------------------------------------------------------
>                 Key: AXIS2-3556
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: codegen
>    Affects Versions: 1.3, nightly
>            Reporter: Paul Fremantle
>             Fix For: 1.4
> If you do
> bin\wsdl2java -uri http://localhost:8081/axis2/services/Version?wsdl -d jaxbri
> you get
> [ERROR] A class/interface with the same name "sample.axisversion.Exception" is already
in use. Use a
>  class customization to resolve this conflict.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message