issues with xmlschema1.4.2.jar and jaxb

2009-06-08 Thread Axis PC
All,

Has anyone faced the following issue?:

1. I have a wsdl which has multiple schema imports. For example

abc.wsdl has x.xsd and y.xsd imports. y.xsd in turn imports
x.xsd.

2. From what I see...xmlschema-1.4.2.jar doesnt like it. In XmlSchema 1.4.x,
the schema collection can only have a single schema instance for a sysid+ns
combination? (read this somewhere). So once I reverted back to
xmlSchema-1.3.x.jar, my scenario started working fine.

Is there any work around for this - without having to replace the newer jar
with the older jar?

I am using axis 1.4.1 and am using jax-ws style web services.

Thanks
Preetham


Re: issues with xmlschema1.4.2.jar and jaxb

2009-06-08 Thread Axis PC
Also...attached is the stacktrace when I use xmlschema-1.4.x.jar

[ERROR] Error occurred while attempting to read generated schema file
{org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in
collection. Namespace: http://schemas.x.com/y/2007/09/mc-description}
[ERROR] Error occurred generating WSDL file for Web service implementation
class {com.x.schemas.y._2008._01.admin.XPortImpl}: {java.lang.Exception:
Error occurred while attempting to read generated schema file
{org.apache.ws.commons.schema.XmlSchemaException: Schema name conflict in
collection. Namespace: http://schemas.x.com/y/2007/09/mc-description}}
java.lang.Exception: Error occurred while attempting to read generated
schema file {org.apache.ws.commons.schema.XmlSchemaException: Schema name
conflict in collection. Namespace:
http://schemas.x.com/y/2007/09/xjob-description}
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.readInSchema(JAXWSRIWSDLGenerator.java:330)
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.generateWsdl(JAXWSRIWSDLGenerator.java:180)
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.initialize(JAXWSRIWSDLGenerator.java:371)
at
org.apache.axis2.jaxws.description.builder.JAXWSRIWSDLGenerator.getWSDL(JAXWSRIWSDLGenerator.java:364)
at
org.apache.axis2.description.AxisService.printWSDL(AxisService.java:1322)
at
org.apache.axis2.transport.http.ListingAgent.processListService(ListingAgent.java:287)
at
org.apache.axis2.transport.http.AxisServlet.doGet(AxisServlet.java:242)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:627)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729)
at
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269)
at
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
at
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
at
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172)
at
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
at
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
at
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
at
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174)
at
org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:875)
at
org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
at
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
at
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
at
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689)
at java.lang.Thread.run(Thread.java:595)


Thanks
Preetham




On Mon, Jun 8, 2009 at 2:52 PM, Axis PC pc.a...@gmail.com wrote:

 All,

 Has anyone faced the following issue?:

 1. I have a wsdl which has multiple schema imports. For example

 abc.wsdl has x.xsd and y.xsd imports. y.xsd in turn imports
 x.xsd.

 2. From what I see...xmlschema-1.4.2.jar doesnt like it. In XmlSchema
 1.4.x, the schema collection can only have a single schema instance for a
 sysid+ns combination? (read this somewhere). So once I reverted back to
 xmlSchema-1.3.x.jar, my scenario started working fine.

 Is there any work around for this - without having to replace the newer jar
 with the older jar?

 I am using axis 1.4.1 and am using jax-ws style web services.

 Thanks
 Preetham