Is there a full stack trace for this?
This is an error that saw a lot when we updated from XmlSchema 1.3.x
to 1.4.x. In XmlSchema 1.4.x, the schema collection can only have a
single schema instance for a sysid+ns combination. 1.3.x used to not
care and would create multiple schemas with the same id+ns. Thus,
I'd have to see where the schemas are being created and back track to
see why there would be multiples with the same id+ns.
Any chance you can send a testcase?
Dan
On May 30, 2008, at 9:46 AM, Daniel Wood wrote:
I've recently upgraded to CXF 2.1 and am now getting the following
error
when I attempt to connect to a service:
org.apache.ws.commons.schema.XmlSchemaException: Schema name
conflict in
collection. Namespace: http://xmlschemas.XXXXX.com/xx_WS
CXF wsdl2java is being used to generate the java classes from the
supplied WSDL during the build cycle, so the application should always
use the current WSDL version. Therefore I am confused as to why I
would
be getting this error as the generated class and the service should be
using the same schema.
Any help would be appreciated.
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
