[#XFIRE-633] Attribute "xsd" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "xsd:element".

XFire

Attribute "xsd" bound to namespace "http://www.w3.org/2000/xmlns/" was already specified for element "xsd:element".

Created: 08/Sep/06 02:41 AM Updated: 01/Oct/06 10:59 PM

Component/s:

None

Affects Version/s:

1.2, 1.2.1

Fix Version/s:

1.2.2

Time Tracking:

Not Specified

File Attachments:	1. xFireTest2.zip (6 kb)
Environment:	xmlbeans 2.2, java 1.42

Description

« Hide

The WSDL generated is invalid - it contains duplicate xsd declarations. An example:

<xsd:element xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="searchResponse" xmlns:xsd="http://www.w3.org/2001/XMLSchema">

All

Comments

Work Log

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Dan Diephouse - 08/Sep/06 09:08 AM

Can you let me know which version of xerces you may or may not have on the classpath?

[ Permlink | « Hide ]

Dan Diephouse - 08/Sep/06 09:09 AM

And also which verison of woodstox?

[ Permlink | « Hide ]

Jakub Mendys - 08/Sep/06 10:00 AM

I cannot find xerces on my classpath (but I cannot guarantee it is not hidded somewhere in WebLogic jars).
I do have woodstox v 2.9.3 on my classpath.

Complete list of jars for the application is as follow (standard Weblogic 8.1 SP3 jars not listed here):
commons-logging/commons-logging-1.0.4.jar
commons-validator/commons-validator-1.1.4.jar
commons-beanutils/commons-beanutils-1.7.0.jar
commons-digester/commons-digester-1.5.0.jar
commons-collections/commons-collections-3.1.0.jar
commons-dbcp/commons-dbcp-1.2.1.jar
commons-pool/commons-pool-1.3.jar
commons-fileupload/commons-fileupload-1.0.jar
commons-lang/commons-lang-2.0.0.jar
struts/struts-1.2.7.jar
log4j/log4j-1.2.8.jar
asm/asm-1.5.3.jar
dom4j/dom4j-1.6.1.jar
hibernate/hibernate-3.1.3.jar
ehcache/ehcache-1.1.jar
cglib/cglib-2.1.3.jar
antrl/antlr-2.7.6rc1.jar
xmlbean/xbean-2.2.0.jar
jaxen/jaxen-1.1-beta-9.jar
xfire/xfire-all-1.1.2.jar
spring/spring-1.2.8.jar
xbean/xbean-spring-2.5.jar
stax/stax-api-1.0.1.jar
activation/activation-1.1.jar
wsdl4j/wsdl4j-1.5.2.jar
woodstox/wstx-asl-2.9.3.jar
jdom/jdom-1.0.jar

[ Permlink | « Hide ]

Dan Diephouse - 08/Sep/06 10:13 AM

Thanks. This issue is driving me insane. I have that exact environment set up but can't reproduce it.

Any chance you could try running this out of weblogic? or could you let me know what jars weblogic has on the classpath? I'm not a classpath expert by any means.

[ Permlink | « Hide ]

Dan Diephouse - 08/Sep/06 10:13 AM

Err I meant to say: I'm not a weblogic expert by any means.

[ Permlink | « Hide ]

Jakub Mendys - 11/Sep/06 05:23 AM

I tried this on tomcat and still get the same problem. The test case is provided:

See test case:
===========================
Under link http://jmendys.com/test.zip you will find a test case to reproduce this problem.

----------------------------------------------------------------------------------------------------------
NOTE!!! Zip contains xfire all 1.1.2 jar with that needs to be replaced with 1.2.1
----------------------------------------------------------------------------------------------------------

The zip contains folder 'test' which is an exploded war ready to deploy. After
deployment is exposes 2 services:

XFireTestService1 (without xmlbean bidings)
XFireTestService2 (with xmlbean bindings)

When you request for WSDL for the second you get invalid xml document but for the first one this seems to work ok.

XMLBeans problem again ?

[ Permlink | « Hide ]

Dan Diephouse - 11/Sep/06 04:56 PM

OK, maybe this is an xmlbeans issue. I'll have to investigate. Thanks for the test case.

[ Permlink | « Hide ]

Jakub Mendys - 19/Sep/06 07:43 AM

test case (maven build)

[ Permlink | « Hide ]

Jakub Mendys - 19/Sep/06 07:43 AM

original test case has been relaced with maven project (attached)

[ Permlink | « Hide ]

Dan Diephouse - 19/Sep/06 10:41 AM

Awesome! Thanks for the test case. I'll be checking this out later today.

[ Permlink | « Hide ]

Dan Diephouse - 22/Sep/06 10:27 AM

Alright, thanks to this test case I have it reproduced now. Working on fixing...

[ Permlink | « Hide ]

Dan Diephouse - 25/Sep/06 12:06 PM

Turns out this is a bug in WSDL4J. To fix, simply drop in a new version of WSDL4J. I've uploaded one here for convenience:

http://envoisolutions.com/~dan/wsdl4j-1.6.jar

[ Permlink | « Hide ]

Dan Diephouse - 01/Oct/06 10:59 PM

OK, I wrote a custom serializer for WSDL4J and things seem to be working fine. If you use a normal WSDL4J and this build, things should work:

http://snapshots.repository.codehaus.org/org/codehaus/xfire/xfire-all/1.2-SNAPSHOT/xfire-all-1.2-20061002.035146-25.jar