Hmmmm....
We updated to XmlSchema to 1.4.2 in the latest releases (2.0.6/2.1) as
it fixes a WHOLE bunch of blocker bugs that users were hitting.
Example, if any of your jaxb beans were final, it would barf.
However, in your stack trace, I see:
org
.apache
.cxf
.service.factory.ReflectionServiceFactoryBean.buildServiceFromClass
Thus, you aren't using a WSDL at runtime. Is there any chance you
could try specifying a wsdl location and seeing if that works? That
may help narrow it down a bit.
Dan
On Jun 6, 2008, at 5:39 AM, Daniel Wood wrote:
Hi Dan, unfortunately I can't send a test case due to the IP on the
wsdl. However, here is the full stack trace:
testRetrieveParties
(xxx.xxx.xxxx.xxx.service.party.PartyManagerServiceIm
plTest) Time elapsed: 1.719 sec <<< ERROR!
org.apache.ws.commons.schema.XmlSchemaException: Schema name
conflict in
collection. Namespace: http://xmlschemas.XXXXXX.com/PartyManager_WS
at
org
.apache.ws.commons.schema.SchemaBuilder.handleXmlSchemaElement(Schema
Builder.java:104)
at
org.apache.ws.commons.schema.SchemaBuilder.build(SchemaBuilder.java:
83)
at
org
.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollectio
n.java:424)
at
org
.apache.ws.commons.schema.XmlSchemaCollection.read(XmlSchemaCollectio
n.java:418)
at
org
.apache.cxf.common.xmlschema.SchemaCollection.read(SchemaCollection.j
ava:118)
at
org
.apache.cxf.databinding.source.AbstractDataBinding.addSchemaDocument(
AbstractDataBinding.java:77)
at
org.apache.cxf.jaxb.JAXBDataBinding.initialize(JAXBDataBinding.java:
326)
at
org
.apache.cxf.service.factory.ReflectionServiceFactoryBean.buildService
FromClass(ReflectionServiceFactoryBean.java:319)
at
org
.apache.cxf.service.factory.ReflectionServiceFactoryBean.initializeSe
rviceModel(ReflectionServiceFactoryBean.java:370)
at
org
.apache.cxf.service.factory.ReflectionServiceFactoryBean.create(Refle
ctionServiceFactoryBean.java:162)
at
org
.apache.cxf.jaxws.support.JaxWsServiceFactoryBean.create(JaxWsService
FactoryBean.java:97)
at
org
.apache.cxf.frontend.AbstractWSDLBasedEndpointFactory.createEndpoint(
AbstractWSDLBasedEndpointFactory.java:74)
at
org
.apache.cxf.frontend.ClientFactoryBean.create(ClientFactoryBean.java:
51)
at
org
.apache.cxf.frontend.ClientProxyFactoryBean.create(ClientProxyFactory
Bean.java:92)
at
xxx
.xxx.xxxx.xxx.service.ServiceImpl.getEndPointInteface(ServiceImpl.jav
a:110)
at xxx.xxx.xxxx.xxx
service
.party.PartyManagerServiceImpl.getInterface(PartyManagerServiceIm
pl.java:23)
at
xxx
.xxx.xxxx.xxx.service.party.PartyManagerServiceImpl.retrieveParties(P
artyManagerServiceImpl.java:39)
at
xxx
.xxx.xxxx.xxx.service.party.PartyManagerServiceImplTest.testRetrieveP
arties(PartyManagerServiceImplTest.java:42)
When did cxf get upgrade to XmlSchema 1.4.x?
Thanks,
Daniel
This transmission is confidential and intended solely for the person
or organisation to whom it is addressed. It may contain privileged
and confidential information. If you are not the intended recipient,
you should not copy, distribute or take any action in reliance on
it. If you have received this transmission in error, please notify
the sender immediately. All messages passing through this gateway
are virus scanned. Any opinions or advice contained in this e-mail
are those of the individual sender except where they are stated to
be the views of RDF Group plc or its subsidiaries, RDF Consulting
(registered number 3522265), RDF Resources (3984500) and Aqua
Resources Group (4975898). RDF Group plc is registered in England at
2 Bartholomews, Brighton, BN1 1HG (registered number 3637683).
---
Daniel Kulp
[EMAIL PROTECTED]
http://www.dankulp.com/blog
