XFire

Generated WSDL elements: duplicate xmlns:xsd attribute

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.2-RC
  • Fix Version/s: 1.2.1
  • Component/s: Core
  • Labels:
    None
  • Environment:
    I'm not using Annotations, this is generated by an XFireExporter from within a Spring Configuration.
  • Number of attachments :
    0

Description

Still testing XFire 1.2RC1, it seems that my previously working configuration (xfire 1.1.1) no longer generates valid WSDL. The Wsdl generated throws the following error in my browser's XML Validator:
XML Parsing Error: duplicate attribute
Location: http://localhost:8081/warfile/MyService?wsdl

This is caused by the following excerpt of WSDL:
<xsd:element xmlns:xsd=" http://www.w3.org/2001/XMLSchema" name="allocateStuff" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="in0" nillable="true" type="tns:Message"/>
<xsd:element maxOccurs="1" minOccurs="1" name="in1" nillable="true" type="xsd:string"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
<xsd:element xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="allocateStuffResponse" xmlns:xsd=" http://www.w3.org/2001/XMLSchema">
<xsd:complexType>
<xsd:sequence>
<xsd:element maxOccurs="1" minOccurs="1" name="out" nillable="true" type="tns:Message"/>
</xsd:sequence>
</xsd:complexType>
</xsd:element>

Dan tells me if there is a problem it will be around line 133 of WSDLBuilder.java , I've looked at this code and I can't immediately see why it wouldn't work as expected, there are no case-mismatch problems for example, very strange, but also very important to fix (for me at least) as my WSDL is completely invalid!

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Jakub Mendys added a comment -

I have the same problem with release 1.2 and xmlbean 2.1.0 and 2.2.0. But works fine in xfire 1.0.2 (which has another bug causing WSDL to grow on each request with a copy of schema)

Show
Jakub Mendys added a comment - I have the same problem with release 1.2 and xmlbean 2.1.0 and 2.2.0. But works fine in xfire 1.0.2 (which has another bug causing WSDL to grow on each request with a copy of schema)
Hide
Permalink
Dan Diephouse added a comment -

I think this might be a problem with the Xmlbeans wsdl builder. Will look into this today as its pretty critical!

Show
Dan Diephouse added a comment - I think this might be a problem with the Xmlbeans wsdl builder. Will look into this today as its pretty critical!
Hide
Permalink
Ciaran Jessup added a comment -

I use Jaxb2 rather than XmlBeans, fwiw ?

Show
Ciaran Jessup added a comment - I use Jaxb2 rather than XmlBeans, fwiw ?
Hide
Permalink
Danny Trieu added a comment -

This has to be critical. Now, none of my XSD working. It complain:

Duplicate attribute. Error processing resource 'http://localhost:8080/rakis-service-1.0-SNAPSHOT/services/RakisService?wsdl...

<xsd:element xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="UserId" type="xsd:string" xmlns:xsd="http://www.w3.org/20...

Dan,
Do you know if we can have a quick fix for this one anytime soon? I tried to roll back to 1.2-RC and the same problem araise....
--danny

Show
Danny Trieu added a comment - This has to be critical. Now, none of my XSD working. It complain: Duplicate attribute. Error processing resource 'http://localhost:8080/rakis-service-1.0-SNAPSHOT/services/RakisService?wsdl... <xsd:element xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="UserId" type="xsd:string" xmlns:xsd="http://www.w3.org/20... Dan, Do you know if we can have a quick fix for this one anytime soon? I tried to roll back to 1.2-RC and the same problem araise.... --danny
Hide
Permalink
Brad Davis added a comment -

I'm getting this as well. The duplicated attribute is the jaxb namespace declaration in the source schema. This ONLY happens for me if I include the path to the JAXB original schema in the services.xml. If I let XFire generate its own schema it doesn't occur.

Show
Brad Davis added a comment - I'm getting this as well. The duplicated attribute is the jaxb namespace declaration in the source schema. This ONLY happens for me if I include the path to the JAXB original schema in the services.xml. If I let XFire generate its own schema it doesn't occur.
Hide
Permalink
Dan Diephouse added a comment -

This is critical. I am working on a solution. I will try to get a fix published tonight, with the goal of doing 1.2.1 this saturday.

Show
Dan Diephouse added a comment - This is critical. I am working on a solution. I will try to get a fix published tonight, with the goal of doing 1.2.1 this saturday.
Hide
Permalink
Dan Diephouse added a comment -

OK, I think I fixed it. I can't reproduce it because I think it depends on the particular DOM implementation that you have.

Could you try this build?

http://snapshots.repository.codehaus.org/org/codehaus/xfire/xfire-all/1.2-SNAPSHOT/xfire-all-1.2-20060830.184652-12.jar

Show
Dan Diephouse added a comment - OK, I think I fixed it. I can't reproduce it because I think it depends on the particular DOM implementation that you have. Could you try this build? http://snapshots.repository.codehaus.org/org/codehaus/xfire/xfire-all/1.2-SNAPSHOT/xfire-all-1.2-20060830.184652-12.jar
Hide
Permalink
Ciaran Jessup added a comment -

Thanks for the fix (assuming it works <g> )

'll do my best to test it, but its tricky because I've had to jump projects so my
code-base isn't quite aligned right, I'll try to get on it in the morning
(uk GMT) . Just out of interest, before the 1.2 release I did try
desperately to flag this issue inside JIRA, but couldn't find a way to do
this, is that because of my user-priveleges or should it always have been
visible [in the 1.2 list of bugs]? [not asking for extra privileges, just concerned this could happen
with other bugs?]
Cheers

  • Ciaran
Show
Ciaran Jessup added a comment - Thanks for the fix (assuming it works <g> ) 'll do my best to test it, but its tricky because I've had to jump projects so my code-base isn't quite aligned right, I'll try to get on it in the morning (uk GMT) . Just out of interest, before the 1.2 release I did try desperately to flag this issue inside JIRA, but couldn't find a way to do this, is that because of my user-priveleges or should it always have been visible [in the 1.2 list of bugs] ? [not asking for extra privileges, just concerned this could happen with other bugs?] Cheers Ciaran
Hide
Permalink
Dan Diephouse added a comment -

Sorry Ciaran, it is my fault for not getting this flagged. Next time feel free to ping the user/dev list. (assuming I didn't miss an email there too....)

Show
Dan Diephouse added a comment - Sorry Ciaran, it is my fault for not getting this flagged. Next time feel free to ping the user/dev list. (assuming I didn't miss an email there too....)
Hide
Permalink
Brad Davis added a comment -

can I get a patch instead of a new build of xfire-all? I'm not using the -all jar and I'm having trouble trying to integrate it into my build.

Show
Brad Davis added a comment - can I get a patch instead of a new build of xfire-all? I'm not using the -all jar and I'm having trouble trying to integrate it into my build.
Hide
Permalink
Dan Diephouse added a comment -

a diff is here: http://svn.xfire.codehaus.org/browse/xfire/trunk/xfire/xfire-core/src/main/org/codehaus/xfire/wsdl11/builder/WSDLBuilder.java?r1=1852&r2=1864

Show
Dan Diephouse added a comment - a diff is here: http://svn.xfire.codehaus.org/browse/xfire/trunk/xfire/xfire-core/src/main/org/codehaus/xfire/wsdl11/builder/WSDLBuilder.java?r1=1852&r2=1864
Hide
Permalink
Jakub Mendys added a comment -

Thank you for the fix

From my perspective (using XMLBeans) the issue has been resolved but unfortunatelly I have reproduced another bug existing from version at least 1.0 (http://jira.codehaus.org/browse/XFIRE-611)

Show
Jakub Mendys added a comment - Thank you for the fix From my perspective (using XMLBeans) the issue has been resolved but unfortunatelly I have reproduced another bug existing from version at least 1.0 ( http://jira.codehaus.org/browse/XFIRE-611 )
Hide
Permalink
Dan Diephouse added a comment -

Marking this as closed as I believe I've fixed it and haven't heard otherwise.

Show
Dan Diephouse added a comment - Marking this as closed as I believe I've fixed it and haven't heard otherwise.
Hide
Permalink
Brad Davis added a comment -

I'm getting a similar problem with duplicate jaxb attributes. This is on the latest release, 1.2.1 I'm working on a repro case to upload.

Show
Brad Davis added a comment - I'm getting a similar problem with duplicate jaxb attributes. This is on the latest release, 1.2.1 I'm working on a repro case to upload.

People

  • Assignee:
    Dan Diephouse
    Reporter:
    Ciaran Jessup
Vote (1)
Watch (4)

Dates

  • Created:
    Updated:
    Resolved: