XML Schema "jpdl-4.4.xsd"

Target Namespace:

Defined Components:

7 global elements, 92 local elements, 12 complexTypes, 5 simpleTypes, 3 element groups, 2 attribute groups

Default Namespace-Qualified Form:

Local Elements: qualified; Local Attributes: unqualified

Schema Location:

/home/aguizar/jbpm/jbpm4/trunk/modules/api/src/main/resources/jpdl-4.4.xsd, see XML source

Annotation

Schema for jPDL 4 process descriptions; the top level element is process.

XML Source

<?xml version="1.0" encoding="UTF-8"?>

Schema for jPDL 4 process descriptions;
the top level element is process.

</documentation>

</annotation>

jBPM Process Definition Language definition.
This is the top level element in a process definition file.

</documentation>

</annotation>

</choice>

</sequence>

The process name. Multiple processes can be deployed with the same
name, as long as they have a different version.

</documentation>

</annotation>

</attribute>

The key can be used to provide a short acronym that replaces the name
as the basis for the generated process definition id.

</documentation>

</annotation>

</attribute>

Indicates the version number of this process definition among its
homonyms. By specifying a version, automatic deployment can tell whether this
process is already deployed.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>Start event.</documentation>

</annotation>

</choice>

</sequence>

<documentation>Resource name of the form in the deployment.</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>End event.</documentation>

</annotation>

</sequence>

</restriction>

</simpleType>

</attribute>

Specify the end state of the execution explicitly.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>End cancel event.</documentation>

</annotation>

</sequence>

</restriction>

</simpleType>

</attribute>

</complexType>

</element>

<documentation>End cancel event.</documentation>

</annotation>

</sequence>

</restriction>

</simpleType>

</attribute>

</complexType>

</element>

Wait state. When an execution arrives in this activity,
the execution stops until an external trigger is delivered through
execution.signal() or execution.getActivityInstance().signal()

</documentation>

</annotation>

</sequence>

</extension>

</complexContent>

</complexType>

</element>

</choice>

</sequence>

</complexType>

</element>

Decision gateway: selects one path out of many alternatives.
When an execution arrives, it takes exactly one outgoing transition.

</documentation>

</annotation>

<documentation>Expression to evaluate.</documentation>

</annotation>

</attribute>

<documentation>Scripting language to interpret.</documentation>

</annotation>

</attribute>

</complexType>

</element>

</sequence>

</extension>

</complexContent>

</complexType>

</element>

</choice>

</sequence>

The script that will be evaluated and resolve to
the name of the outgoing transition.

</documentation>

</annotation>

</attribute>

Identification of the scripting language
to use for the expr attribute.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

Spawns concurrent paths of execution
over each element of a collection.

</documentation>

</annotation>

</choice>

</sequence>

</complexType>

</element>

Spawns multiple concurrent paths of
execution.

</documentation>

</annotation>

</choice>

</sequence>

</complexType>

</element>

Spawns multiple concurrent paths of
execution.

</documentation>

</annotation>

</choice>

</sequence>

</restriction>

</simpleType>

</attribute>

</complexType>

</element>

<documentation>Evaluates a piece of text as a script.</documentation>

</annotation>

</choice>

</extension>

</complexContent>

</complexType>

</element>

<documentation>Performs a Hibernate query.</documentation>

</annotation>

</choice>

</extension>

</complexContent>

</complexType>

</element>

<documentation>Performs a Hibernate SQL query.</documentation>

</annotation>

</choice>

</extension>

</complexContent>

</complexType>

</element>

<documentation>Sends an email.</documentation>

</annotation>

</choice>

</extension>

</complexContent>

</complexType>

</element>

<documentation>Sends an email.</documentation>

</annotation>

</choice>

</extension>

</complexContent>

</complexType>

</element>

Invokes a method on a java object.
Either the java class is instantiated with reflection,
or the java object is fetched from the environment.
Values are then injected into the fields and.
Finally a method is invoked.

</documentation>

</annotation>

</choice>

</extension>

</complexContent>

</complexType>

</element>

<documentation>Assigns a source value to a target location.</documentation>

</annotation>

</choice>

</extension>

</complexContent>

</complexType>

</element>

Calls a user defined, custom implementation of
ActivityBehaviour.

</documentation>

</annotation>

</sequence>

</extension>

</complexContent>

</complexType>

</element>

</choice>

</extension>

</complexContent>

</complexType>

</element>

<documentation>Creates a task in the task component.</documentation>

</annotation>

</complexType>

</element>

</complexType>

</element>

</sequence>

</extension>

</complexContent>

</complexType>

</element>

</choice>

</sequence>

<documentation>Resource name of the form in the deployment.</documentation>

</annotation>

</attribute>

</restriction>

</simpleType>

</attribute>

</complexType>

</element>

Waits while a sub process instance is being executed
and continues when the sub process instance ends.

</documentation>

</annotation>

<documentation>Events on which listeners can be registered.</documentation>

</annotation>

</element>

</complexType>

</element>

</complexType>

</element>

</sequence>

</extension>

</complexContent>

</complexType>

</element>

</choice>

</sequence>

References a sub-process by id. This means that a specific
version of a process definition is referenced.

</documentation>

</annotation>

</attribute>

References a sub-process by key. Therefore, the latest
version of the process definition with the given key is referenced.
The latest version is resolved in each execution.

</documentation>

</annotation>

</attribute>

Expression that is evaluated when the sub process instance ends.
The value is then used for outcome transition mapping.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>Scope enclosing a number of activities.</documentation>

</annotation>

<documentation>Events on which listeners can be registered.</documentation>

</annotation>

</element>

</choice>

</sequence>

</complexType>

</element>

Selects one outgoing transition based on evaluation
of rules.

</documentation>

</annotation>

<documentation>Events on which listeners can be registered.</documentation>

</annotation>

</element>

</choice>

</sequence>

</complexType>

</element>

Evaluates rules after feeding in some facts in a stateful
knowledge session.

</documentation>

</annotation>

</complexType>

</element>

</sequence>

<documentation>Expression to evaluate.</documentation>

</annotation>

</attribute>

<documentation>Script language to interpret.</documentation>

</annotation>

</attribute>

</complexType>

</element>

</sequence>

</extension>

</complexContent>

</complexType>

</element>

<documentation>Events on which listeners can be registered.</documentation>

</annotation>

</element>

</choice>

</sequence>

</complexType>

</element>

</choice>

</group>

<documentation>The null value.</documentation>

</annotation>

</element>

Reference to an object in the current environment.

</documentation>

</annotation>

<documentation>The name of the referred object.</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>The current environment.</documentation>

</annotation>

</element>

<documentation>JNDI lookup based off the initial context.</documentation>

</annotation>

</complexType>

</element>

<documentation>java.util.List instance.</documentation>

</annotation>

</choice>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

<documentation>List implementation class.</documentation>

</annotation>

</attribute>

Indicates if this collection should be synchronized
with Collections.synchronizedList()

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>java.util.Set instance.</documentation>

</annotation>

</choice>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

<documentation>Set implementation class.</documentation>

</annotation>

</attribute>

Indicates if this collection should be synchronized
with Collections.synchronizedSet()

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>java.util.Properties instance.</documentation>

</annotation>

</complexType>

</element>

</choice>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

<documentation>File in the file system.</documentation>

</annotation>

</attribute>

<documentation>Resource in the classpath.</documentation>

</annotation>

</attribute>

<documentation>Resource in the web.</documentation>

</annotation>

</attribute>

tells whether the resource referenced by
attributes 'file', 'resource' or 'url' is XML. The default is the
plain properties format, where a space or '=' separates the key
from the value in each line.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>8-bit signed integer.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>16-bit Unicode character.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</restriction>

</simpleType>

</attribute>

</complexType>

</element>

<documentation>64-bit floating point number.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>Boolean false value</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>32-bit floating point number.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>32-bit signed integer.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>64-bit signed integer.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>16-bit signed integer.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>Boolean true value.</documentation>

</annotation>

The name of the object. Optional, serves as an identifier
to refer to this object from other object descriptions.
Also used to fetch the object programmatically.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

</choice>

</group>

Any java object that will be created by reflection.

There are three main ways to create an object: by constructor or by a factory
object or a static factory method.

Using the constructor

: the

<code>class</code>

attribute must provide
the fully qualified class name. In case a constructor other than the default
should be invoked, a

<code>constructor</code>

child element can be provided.
The

<code>factory</code>

attribute should be absent when using a constructor.

Using a factory

: the

<code>factory</code>

attribute or one

<code>factory</code>

element must be provided along with the attribute

<code>method</code>

Using a static factory method

: the

<code>class</code>

and

<code>method</code>

attributes should be specified. There should not be a

<code>factory</code>

attribute or element.

Construction and initialization

: all objects (constructor and factory)
are build in two phases: construction and initialisation phase. During construction
all is done until a pointer is obtained to the object. In initialisation, operations
are applied to the object until it is ready to be used. The separation between
construction and initialisation is made to allow for bidirectional references.

Operations

: after construction, various operations can be applied to objects
like e.g. direct field injection, injection through setters, method invocation,
enlist with the standard transaction, subscribe the object to an observable.

Arguments

: there are two different places for arguments. The

elements for the factory method invocation should be placed as child elements under
the

<code>object</code>

element. The

elements for the constructor
should be placed as child elements of the

<code>constructor</code>

element.

</documentation>

</annotation>

Contains one element that describes the factory object.

</documentation>

</annotation>

</complexType>

</element>

Specifies the arguments for a non-default constructor.

</documentation>

</annotation>

</choice>

</complexType>

</element>

<documentation>The factory method arguments.</documentation>

</annotation>

</element>

Injects a value into a member field of this object.
Exactly one child element must specify the value.

</documentation>

</annotation>

<documentation>Member field name.</documentation>

</annotation>

</attribute>

</complexType>

</element>

Injects a value through a setter method.
Exactly one child element must specify the value.

</documentation>

</annotation>

<documentation>Name of the property (without the 'set' prefix).</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>Invokes a method.</documentation>

</annotation>

</choice>

<documentation>Method name.</documentation>

</annotation>

</attribute>

</complexType>

</element>

</choice>

<documentation>Fully qualified class name</documentation>

</annotation>

</attribute>

<documentation>Expression that provides the object.</documentation>

</annotation>

</attribute>

<documentation>Script language to interpret.</documentation>

</annotation>

</attribute>

<documentation>Name of the factory object.</documentation>

</annotation>

</attribute>

<documentation>Factory method name</documentation>

</annotation>

</attribute>

Indicates if the member fields and setter properties
should be wired automatically based on matching the property names and types
with the object names and types.

</documentation>

</annotation>

</attribute>

<documentation>Indicates if the user code should be cached.</documentation>

</annotation>

</attribute>

</complexType>

The method arguments.
Each 'arg' element should have exactly one child
element that represents the value of the argument.

</documentation>

</annotation>

Class name representing the method type.
Optional, helps resolve the appropriate method in case of overloading.

</documentation>

</annotation>

</attribute>

</complexType>

<documentation>java.util.Map instance.</documentation>

</annotation>

</complexType>

</element>

</complexType>

</element>

</sequence>

</complexType>

</element>

</sequence>

<documentation>Map implementation class.</documentation>

</annotation>

</attribute>

Indicates if this collection should be synchronized
with Collections.synchronizedCollection()

</documentation>

</annotation>

</attribute>

</complexType>

<documentation>Field injections from the environment invocation.</documentation>

</annotation>

</element>

<documentation>Method arguments.</documentation>

</annotation>

</element>

</choice>

</sequence>

<documentation>The name of the method to invoke.</documentation>

</annotation>

</attribute>

The jndi name of the ejb that needs to be invoked.

</documentation>

</annotation>

</attribute>

<documentation>The class to instantiate.</documentation>

</annotation>

</attribute>

Expression that resolves to the target object
on which the method should be invoked.

</documentation>

</annotation>

</attribute>

The language in which attribute 'expr' is to be
resolved.

</documentation>

</annotation>

</attribute>

<documentation>The variable name to store the return value.</documentation>

</annotation>

</attribute>

</complexType>

The text content of this element is the script to evaluate.
This element and the expression attribute are mutually exclusive.

</documentation>

</annotation>

</element>

</sequence>

The value of this attribute is the script to evaluate.
This attribute and the text element are mutually exclusive.

</documentation>

</annotation>

</attribute>

<documentation>Identifies the scripting language in use.</documentation>

</annotation>

</attribute>

Name of the variable in which the result
of the script evaluation will be stored.

</documentation>

</annotation>

</attribute>

</complexType>

<documentation>Descriptor that constructs the source value.</documentation>

</annotation>

</complexType>

</element>

</sequence>

<documentation>Expression that resolves the source value.</documentation>

</annotation>

</attribute>

<documentation>Language in which from-expr is written.</documentation>

</annotation>

</attribute>

<documentation>Variable that provides the source value.</documentation>

</annotation>

</attribute>

<documentation>Expression that resolves the target location.</documentation>

</annotation>

</attribute>

<documentation>Variable that provides the target location.</documentation>

</annotation>

</attribute>

</complexType>

<documentation>Query text.</documentation>

</annotation>

</element>

<documentation>Query parameters.</documentation>

</annotation>

</sequence>

</complexType>

</element>

</sequence>

Name of the variable in which the result
of the script evaluation will be stored.

</documentation>

</annotation>

</attribute>

<documentation>Tells whether the query returns a unique result.</documentation>

</annotation>

</attribute>

</complexType>

Name of this activity. The name should be unique
in the complete scope of the process.

</documentation>

</annotation>

</attribute>

Graphical information used by process designer tool.

</documentation>

</annotation>

</attribute>

<documentation>Specifies async continuation.</documentation>

</annotation>

</attribute>

</attributeGroup>

</restriction>

</simpleType>

The assignment attributes are used in
tasks and swimlanes to specify who is the assignee.

</documentation>

</annotation>

Expression that resolves to a userId referencing
the person to whom the task or swimlane will be assigned.

</documentation>

</annotation>

</attribute>

<documentation>Expression language for the assignee attribute.</documentation>

</annotation>

</attribute>

Expression that resolves to a comma separated
list of userIds. All the referred people will be candidates for
take the task or swimlane.

</documentation>

</annotation>

</attribute>

Expression language for the
candidate-users attribute.

</documentation>

</annotation>

</attribute>

Resolves to a comma separated list of groupIds.
All the referred people will be candidates to
take the task or swimlane.

</documentation>

</annotation>

</attribute>

Expression language for the
candidate-groups attribute.

</documentation>

</annotation>

</attribute>

</attributeGroup>

<documentation>Process role.</documentation>

</annotation>

</sequence>

</complexType>

</element>

The outgoing transitions. The first in the list
will be the default outgoing transition.

</documentation>

</annotation>

</sequence>

<documentation>Name of this outgoing transition</documentation>

</annotation>

</attribute>

Name of the destination activity of this transition.

</documentation>

</annotation>

</attribute>

Graphical information used by process designer tool.

</documentation>

</annotation>

</attribute>

</complexType>

<documentation>Link from one activity to another.</documentation>

</annotation>

</element>

List of event listeners that will
be notified when the event is fired

</documentation>

</annotation>

</group>

</sequence>

Event identification. start, end, take or
any other custom event.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>Name of the sub process variable.</documentation>

</annotation>

</attribute>

<documentation>Expression that provides the variable value.</documentation>

</annotation>

</attribute>

<documentation>Language of the expression.</documentation>

</annotation>

</attribute>

Name of the process variable
in the super process.

</documentation>

</annotation>

</attribute>

</complexType>

List of event listeners that will
be notified when the timer fires.

</documentation>

</annotation>

</sequence>

Timer duedate expression that defines the duedate of this
timer relative to the creation time of the timer.
E.g. '2 hours' or '4 business days'.

</documentation>

</annotation>

</attribute>

Timer duedate expression that defines repeated scheduling
relative to the last timer fire event.
E.g. '2 hours' or '4 business days'

</documentation>

</annotation>

</attribute>

Absolute time in the format

.
The format can be customized in the configuration.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

<documentation>Explicit variable declaration.</documentation>

</annotation>

</sequence>

Name of the variable. Must differ from other variable
names.

</documentation>

</annotation>

</attribute>

<documentation>Type of the variable.</documentation>

</annotation>

</attribute>

</annotation>

</attribute>

</complexType>

</element>

</extension>

</complexContent>

</complexType>

</element>

</extension>

</complexContent>

</complexType>

</element>

</extension>

</complexContent>

</complexType>

</element>

</extension>

</complexContent>

</complexType>

</element>

</extension>

</complexContent>

</complexType>

</element>

</extension>

</complexContent>

</complexType>

</element>

</extension>

</complexContent>

</complexType>

</element>

</choice>

</group>

<documentation>Resource in the web.</documentation>

</annotation>

</attribute>

<documentation>Resource in the classpath.</documentation>

</annotation>

</attribute>

<documentation>Path in the file system.</documentation>

</annotation>

</attribute>

</complexType>

</element>

</sequence>

</complexType>

</element>

</sequence>

</extension>

</complexContent>

</complexType>

</choice>

<documentation>JNDI name of the connection factory.</documentation>

</annotation>

</attribute>

<documentation>JNDI name of the destination.</documentation>

</annotation>

</attribute>

Tells whether the message should be sent in a transaction.

</documentation>

</annotation>

</attribute>

<documentation>Indicates the acknowledgment mode.</documentation>

</annotation>

</attribute>

</complexType>

List of email addresses separated by ',' (comma)
or whitespace.

</documentation>

</annotation>

</attribute>

List of users, resolved to email addresses thought
the configured identity component. Users are separated by ',' (comma)
';' (semicolon) or whitespace.

</documentation>

</annotation>

</attribute>

List of groups, that are resolved to the email address against
configured identity component. Groups are separated by ',' (comma)
';' (semicolon) or whitespace

</documentation>

</annotation>

</attribute>

</complexType>

</restriction>

</simpleType>

</restriction>

</simpleType>

<documentation>Reference to the email template.</documentation>

</annotation>

</simpleType>

Information to migrate instances of previously deployed
process definitions to the new version.

</documentation>

</annotation>

The migration handler specifies the name of a class to be executed
while migrating the process instance.

</documentation>

</annotation>

</complexType>

</element>

One activity mapping will be present for each activity of which the
name changed.

</documentation>

</annotation>

Name of the activity in the previously deployed
process definition.

</documentation>

</annotation>

</attribute>

Name of the activity in the newly deployed
process definition.

</documentation>

</annotation>

</attribute>

</complexType>

</element>

</choice>

</complexType>

</element>

</restriction>

</simpleType>

</schema>

This XML schema documentation has been generated with DocFlex/XML RE 1.7.2 using DocFlex/XML XSDDoc 2.1.0 template set.

DocFlex/XML RE is a reduced edition of DocFlex/XML, which is a tool for programming and running highly sophisticated documentation and reports generators by the data obtained from any kind of XML files. The actual doc-generators are implemented in the form of special templates that are designed visually using a high quality Template Designer GUI basing on the XML schema (or DTD) files describing the data source XML.

DocFlex/XML XSDDoc is a commercial template application of DocFlex/XML that implements a high-end XML Schema documentation generator with simultaneous support of framed multi-file HTML, single-file HTML and RTF output formats. (More formats are planned in the future).

A commercial license for "DocFlex/XML XSDDoc" will allow you:

To configure the generated documentation so much as you want. Thanks to our template technology, it was possible to support more than 300 template parameters (working the same as "options" of an ordinary doc-gen), which will give you an unprecedented control over the generated content!
To use certain features disabled in the free mode (such as the full documenting of substitution groups).
To enable/disable documenting of the initial, imported, included and redefined XML schemas selectively.
To document local element components both globally and locally (similar to attributes).
To enable/disable reproducing of namespace prefixes.
To format your annotations with XHTML tags and reproduce that formatting both in HTML and RTF output.
To insert images in your annotations using XHTML <img> tags (supported both in HTML and RTF output).
To use PlainDoc.tpl main template to generate all the XML schema documentation in the form of a single HTML file.
To use the same template to generate the incredible quality RTF documentation.
To document only selected XML schema components specified by name.
To remove this very advertisement text

Once having only such a license, you will be able to run the fully-featured XML schema documentation generator both with DocFlex/XML SDK and with DocFlex/XML RE, which is a reduced free edition containing only the template interpretor / output generator. No other licenses will be required!

But this is not all. In addition to it, a commercial license for DocFlex/XML SDK will allow you to modify the XSDDoc templates themselves as much as you want. You will be able to achieve whatever was impossible to do with the template parameters only. And, of course, you could develop any template applications by your own!

Please note: By purchasing a license for this software, you not only acquire a useful tool, you will also make an important investment in its future development, the result of which you could enjoy later by yourself. Every single your purchase matters and makes a difference for us!

To buy a license, please follow this link: http://www.filigris.com/shop/