[CXF-2548] Aegis component attempts to assign new schema objects with an existing namespace URI to ServiceInfo if consecutive Clients are created for the same WSDL causing XmlSchemaException: Schema name conflict in collection

• Type: Bug
• Status: Closed
• Priority: Critical
• Resolution: Cannot Reproduce
• Affects Version/s: 2.2.5, 2.2.6
• Fix Version/s: Invalid
• Component/s: Aegis Databinding

Environment

BEA JRockit 1.6.0 + WebLogic 10.3, Sun JDK 1.6.0

• Assignee: Unassigned
• Reporter: Antal Varga
• Created: 18/Nov/09 17:09
• Updated: 27/Jan/16 16:46
• Resolved: 07/Jan/10 18:40

Description

Revision 826052 changed the behaviour of org.apache.cxf.frontend.ClientFactoryBean.create() so that subsequent calls will create new Client objects.

The ServiceInfos are cached between the creation of these objects so that the SchemaCollection objects assigned to them also remain the same.

However when an endpoint is created (it is called for both of the Clients) and org.apache.cxf.aegis.databinding.AegisDatabinding.createSchemas()
is run then (line 457) a new SchemaInfo is attempted to be added to the schema collection with a namespace URI already in the collection
(see API component org.apache.cxf.service.model.ServiceInfo.addNewSchema(String)) because it was already added
during the creation of the previous Client object.

I think prior to adding the new SchemaInfo it should be checked if an entry with the given namespace URI already exists.