See information about the latest product version
Naming conventions in applications and libraries
When adding resources to applications and libraries, ensure that you use appropriate naming conventions to avoid conflicts. For example, you can qualify a file path with a library name, or differentiate a schema element by using a QName.
A QName refers to a namespace-qualified element from a message model, which can be an XML schema, DFDL schema file, or a message set. These QNames must be unique throughout an application or library and any of their referenced libraries. For example, "Application1" contains two schema files, schemaOne.xsd and schemaTwo.xsd. Both schema files contain the element "sameElement", which is qualified by the namespace http://mynamespace.com. This naming convention causes a conflict because both schema files have the same QName for the element named "sameElement", which is qualified by the same namespace.
Both schema files also contain the element "diffNSElement", but this element is qualified by a different namespace in each schema file. Therefore, no conflict occurs. If a conflict of QNames is detected, each XML or DFDL schema file, or message set, that contains a construct with that QName is marked with an error in the Broker Development view and Problems view.
- An XSD resource name and path pair
- A WSDL resource name and path pair
- A message flow resource name and path pair
- An adapter resource name and path pair (.inadapter and .outadapter)
- A CORBA IDL resource name and path pair
- A message map resource name and path pair (.map)
- An XSLT resource name and path pair
- A PHP resource name and path pair
- Two separate applications and adapter libraries for inbound and outbound operations
- A single adapter library with both inbound and outbound adapters that are generated in different namespaces and used in two separate applications. In this configuration, one application must have an inbound flow, and the other must have an outbound flow.
- A single adapter library with both inbound and outbound adapters. These adapters must be generated in different namespaces and used in one application with both inbound and outbound flows.
- Two separate applications that have their own business object schema, adapter and flows.