XML Schema Components

You can catalog XML Schema Definitions (XSD) components and use them in your BPM project. Use XML Schema components for parsing, validating, manipulating and generating typed XML documents.

Supported XML Schema languages

Oracle BPM supports the XML Schema Definition (XSD) language versions 1.0 and 1.1.

Other XML schema languages, such as like DTD (Document Type Definition) are not currently supported. Third party tools exist to convert other schema languages into XSD.

Not using Schemas

If you need to perform ad-hoc XML parsing and general XML processing without using schemas, refer to the standard Fuego.Xml.XMLDocument and Fuego.Xml.XMLNode components.

Cataloging XML Schema
Before using XML Schema components from processes or BPM Objects, you must include them into the project catalog. When you catalog a component, you are gathering all the necessary information that Studio needs in order to call and execute it at runtime.
Using XML Schema Components
Use XML Schema components for parsing, validating, manipulating and generating typed XML documents.
XML Schema Examples
An example of using XML Schema Definition representing customer information.
Important Considerations
Advanced information you may need to know when working with cataloged XML Schema components.
Mapping XSD to BPM Components
This sections explains how XML Schema Definition (XSD) types map to BPM components and PBL types when cataloging XSD components.

Parent topic: External Components