Namespace:	http://jbpm.org/4.0/jpdl
Content:	complex, 6 attributes, 6 elements
Defined:	globally in jpdl-4.0.xsd, see XML source
Includes:	definitions of 6 attributes and 6 elements
Used:	at 5 locations

XML Representation Summary
<...
	auto-wire	=	string
	class	=	string
	expr	=	string
	factory	=	string
	lang	=	string
	method	=	string
	>
	Content:  (tns:factory | tns:constructor | tns:arg | tns:field | tns:property | tns:invoke)*
</...>

• As direct type of elements (4):

  tns:assignment-handler (in tns:task), tns:event-listener (type tns:wireObjectType),

  tns:handler (in tns:decision), tns:object (type tns:wireObjectType)

• In derivations of anonymous types of elements (1):

  tns:custom (type extension of tns:wireObjectType) (as extension base)

Any java object that will be created by reflection. . <p>There are three main ways to create an object: by constructor or by a factory object or a static factory method.</p> <p><b>Using the constructor</b>: Then the <code>class</code> attribute must provide the fully qualified class name. In case another constructor then the default is targetted, a <code>constructor</code> child element can be provided. The <code>factory</code> attribute should not be provided for using a constructor. </p> <p><b>Using a factory</b>: Then the <code>factory</code> attribute or one <code>factory</code> element must be provided along with the attribute <code>method</code>. </p> <p><b>Using a static factory method</b>: Then the <code>class</code> and <code>method</code> attributes should be specified. There should be no reference to a <code>factory</code> attribute of element. </p> <p><b>Construction and initialization</b>: 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. In that case, at least one of both ends can not be fully initialised before it is injected into the other end. </p> <p><b>Operations</b>: 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 as a listener to an observable </p> <p><b>Arguments</b>: There are two different places for arguments. The <code>arg</code> elements for the factory method invocation should be placed as child elements under the <code>object</code> element. The <code>arg</code> elements for the constructor should be placed as child elements under the <code>constructor</code> element. </p>

<complexType name="wireObjectType"> <annotation> <documentation> Any java object that will be created by reflection. . <p> There are three main ways to create an object: by constructor or by a factory object or a static factory method. </p> <p> <b>Using the constructor</b> : Then the <code>class</code> attribute must provide the fully qualified class name. In case another constructor then the default is targetted, a <code>constructor</code> child element can be provided. The <code>factory</code> attribute should not be provided for using a constructor. </p> <p> <b>Using a factory</b> : Then the <code>factory</code> attribute or one <code>factory</code> element must be provided along with the attribute <code>method</code> . </p> <p> <b>Using a static factory method</b> : Then the <code>class</code> and <code>method</code> attributes should be specified. There should be no reference to a <code>factory</code> attribute of element. </p> <p> <b>Construction and initialization</b> : 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. In that case, at least one of both ends can not be fully initialised before it is injected into the other end. </p> <p> <b>Operations</b> : 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 as a listener to an observable </p> <p> <b>Arguments</b> : There are two different places for arguments. The <code>arg</code> elements for the factory method invocation should be placed as child elements under the <code>object</code> element. The <code>arg</code> elements for the constructor should be placed as child elements under the <code>constructor</code> element. </p> </documentation> </annotation> <choice maxOccurs="unbounded" minOccurs="0"> <element name="factory"> <annotation> <documentation> Contains one element that describes the factory object. </documentation> </annotation> <complexType> <group ref="tns:wireObjectGroup"/> </complexType> </element> <element name="constructor"> <annotation> <documentation> Specifies the arguments to use for a non-default constructor. </documentation> </annotation> <complexType> <choice maxOccurs="unbounded"> <element name="arg" type="tns:argType"/> </choice> </complexType> </element> <element name="arg" type="tns:argType"> <annotation> <documentation>The factory method arguments.</documentation> </annotation> </element> <element name="field"> <annotation> <documentation> Injects a value into a member field of this object. Exactly one child element must specify the value. </documentation> </annotation> <complexType> <group ref="tns:wireObjectGroup"/> <attribute name="name"> <annotation> <documentation>The member field name</documentation> </annotation> </attribute> </complexType> </element> <element name="property"> <annotation> <documentation> Injects a value through a setter method. Exactly one child element must specify the value. </documentation> </annotation> <complexType> <group ref="tns:wireObjectGroup"/> <attribute name="name"> <annotation> <documentation> The name of the property (without the 'set' prefix) </documentation> </annotation> </attribute> </complexType> </element> <element name="invoke"> <annotation> <documentation>Invokes a method</documentation> </annotation> <complexType> <choice maxOccurs="unbounded" minOccurs="0"> <element name="arg" type="tns:argType"/> </choice> <attribute name="method" type="string" use="required"> <annotation> <documentation>the method name</documentation> </annotation> </attribute> </complexType> </element> </choice> <attribute name="class" type="string"> <annotation> <documentation>The fully qualified class name</documentation> </annotation> </attribute> <attribute name="expr" type="string"> <annotation> <documentation> The class to instantiate. </documentation> </annotation> </attribute> <attribute name="lang" type="string"> <annotation> <documentation> The class to instantiate. </documentation> </annotation> </attribute> <attribute name="factory" type="string"> <annotation> <documentation>The name of the factory object</documentation> </annotation> </attribute> <attribute name="method" type="string"> <annotation> <documentation>The factory method name</documentation> </annotation> </attribute> <attribute name="auto-wire" type="string"> <annotation> <documentation> Indicates if the member fields and setter properties should be automatically wired based on matching the property names and types with the object names and types </documentation> </annotation> </attribute> </complexType>

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/