Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 1.2.3
-
Fix Version/s: None
-
Component/s: None
-
Labels:None
-
Environment:xfire: 1.2.3
oc4j - Oracle Containers for J2EE 10g (10.1.3.1)
Tomcat - apache-tomcat-5.5.20
-
Number of attachments :
Description
debugged using soap ui 1.6.
using xfire: 1.2.3
I have my application using xfire for web services and I found strange thing.
Under Tomcat everything works fine and the same WAR under OC4J generates duplicate attribute 'xmlns:xsd' in <xsd:schema element.
I had similar problem width Tomcat too but it was fixed in 1.2.1 or 1.2.2.
error log message:
Wed Jan 03 08:54:50 CET 2007:ERROR:Error importing wsdl: org.apache.xmlbeans.XmlException: error: duplicate attribute 'xmlns:xsd'
oc4j - Oracle Containers for J2EE 10g (10.1.3.1)
Wed Jan 03 08:54:50 CET 2007:DEBUG:<< "<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" targetNamespace="http://xxxx.axonpro.sk" elementFormDefault="qualified" attributeFormDefault="qualified" xmlns:xsd="http://www.w3.org/2001/XMLSchema">[\r][\n]"
i have search-local-classes-first="true" in my deployment plan,
<web-app-class-loader search-local-classes-first="true">
I added xalan to my classpath to fix
java.lang.ClassCastException: oracle.xml.jaxp.JXSAXTransformerFactory
at javax.xml.transform.TransformerFactory.newInstance(Unknown Source)
now it works widthout exception, but it generates duplicate attribute 'xmlns:xsd' in <xsd:schema element
---------------------
Tomcat - apache-tomcat-5.5.20
Wed Jan 03 09:29:58 CET 2007:DEBUG:<< "<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" attributeFormDefault="qualified" elementFormDefault="qualified" targetNamespace="http://xxxx.axonpro.sk">[\r][\n]"
everything works fine...
---------------------
I'm really confused.
thanx for any help
It's strange.
I added
serializer.jar
wstx-asl-3.0.1.jar
xalan.jar
xfire-jsr181-api-1.0-M1.jar
XmlSchema-1.1.jar
to my application classpath
and now it generates valid WSDL.
perhaps this will help to someone.
sorry for opening new issue...