[ 
http://jira.codehaus.org/browse/XFIRE-1019?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_105909
 ] 

Nicholas Kum commented on XFIRE-1019:
-------------------------------------

Hi Eric,

Have you seen my jira issue?
http://jira.codehaus.org/browse/XFIRE-1071

It contains a patch for WSDLBuilder.java
I might not be the best fix, but it seems to do the trick :)
I couldn't find a way to configure xfire to get around this problem so it 
probably is a bug. 

I didn't notice your jira issue until I tried googling mine.

Regards
Nick

> WSDL Generation inserting duplicate elements for JAXB provided schema
> ---------------------------------------------------------------------
>
>                 Key: XFIRE-1019
>                 URL: http://jira.codehaus.org/browse/XFIRE-1019
>             Project: XFire
>          Issue Type: Bug
>    Affects Versions: 1.2.5, 1.2.6
>         Environment: Fedora 7, jdk 1.5.0_12, Spring 2.0.5, Tomcat 5.5.23
>            Reporter: Eric Miles
>            Assignee: Dan Diephouse
>         Attachments: wsdl-test.zip
>
>
> Ok, attached is a sample project (really small, eclipse and maven enabled) 
> that identifies this exact issue.
> Also, here is a snippet of the problematic WSDL:
> <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"; 
> xmlns:ns="http://test.mycompany.com/services/WsdlTestService"; 
> elementFormDefault="qualified" 
> targetNamespace="http://test.mycompany.com/services/WsdlTestService";> 
>       
>       <xsd:complexType name="BaseType">
>               <xsd:sequence>
>                       <xsd:element name="Item" type="xsd:int"/>
>                       <xsd:element name="SecondItem" type="xsd:string"/>
>               </xsd:sequence>
>       </xsd:complexType>
>               <xsd:element name="OperationOne" type="ns:BaseType"/>
>       
>       <xsd:element name="OperationTwo" type="ns:BaseType"/>
>       
> <xsd:element name="OperationTwo" type="tns:BaseType"/>
> <xsd:element name="OperationOne" type="tns:BaseType"/>
> </xsd:schema>
> As you can see, at the end of the schema XFire or WSDL4J is inserting 2 new 
> elements for element that have ALREADY been defined.  Not only that, these 
> are using a namespace prefix that I have not identified on my schema (tns).  
> So this is coming from XFire or WSDL4j.  I've tried changing my namespace 
> prefix to be tns with no different result.
> Thoughts?
> On Tue, 2007-05-29 at 13:29 -0400, Eric Miles wrote:
> This is an odd problem that I'm having a hard time tracking down.  I am doing 
> schema first development, generating Impl classes with JAXB2.  I'm using 
> Xfire 1.2.5, Spring 2.0, and JAXB2.  I have my schema defined as such:
> > 
> > <xsd:element name="SyncLeave" type="ns:SyncLeavePremPay" />
> > 
> > <xsd:element name="SyncPremPay" type="ns:SyncLeavePremPay" />
> > 
> > <xsd:complexType name="SyncLeavePremPay">
> > <xsd:sequence>
> > <xsd:element name="Error" type="ns:Error" minOccurs="0" 
> > maxOccurs="unbounded" />
> > <xsd:element name="InsLeavePrem" type="ns:InsLeavePrem"
> > minOccurs="0" maxOccurs="unbounded"></xsd:element>
> > </xsd:sequence>
> > </xsd:complexType>
> > 
> > 
> > My interface as such:
> > 
> > @WebMethod(operationName = "SyncLeave")
> > @WebResult( name = "SyncLeave" )
> > public SyncLeavePremPay syncLeave(
> > @WebParam(name = "SyncLeave")SyncLeavePremPay body);
> > 
> > @WebMethod(operationName = "SyncPremPay")
> > @WebResult( name = "SyncPremPay" )
> > public SyncLeavePremPay syncPremPay(
> > @WebParam(name = "SyncPremPay")SyncLeavePremPay body);
> > 
> > However, when I use XFire to generate my WSDL based on the interface and my 
> > provided schema, XFire is adding duplicate elements for SyncLeave and 
> > SyncPremPay
> > 
> > At the end of the schema I have provided, it seems as though XFire is 
> > entering it's own definition for these 2 elements as seen here:
> > 
> > ...
> > </xsd:complexType> 
> >     </xsd:element>
> > 
> > <xsd:element name="SyncLeave" type="tns:SyncLeavePremPay"/>
> > <xsd:element name="SyncPremPay" type="tns:SyncLeavePremPay"/>
> > </xsd:schema>
> > 
> > Keep in mind, these 2 elements are already defined further up in my schema. 
> >  Why is XFire doing this?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to