element <tns:migrate-instances>
Namespace:
http://jbpm.org/4.4/jpdl
Type:
anonymous complexType
Content:
complex, 1 attribute, 2 elements
Defined:
globally in jpdl-4.4.xsd, see XML source
Includes:
definitions of 1 attribute and 2 elements
Used:
at 1 location
XML Representation Summary
<tns:migrate-instances
    action
 = 
 ("end" | "migrate") : "migrate"
    >
   
Content: 
 (tns:migration-handler | tns:activity-mapping)*
</tns:migrate-instances>
Content model elements (2):
tns:activity-mapping (in tns:migrate-instances),
tns:migration-handler (in tns:migrate-instances)
Included in content model of elements (1):
tns:process
Known Usage Locations
Annotation
Information to migrate instances of previously deployed process definitions to the new version.
XML Source (see within schema source)
<element name="migrate-instances">
<annotation>
<documentation>
Information to migrate instances of previously deployed
process definitions to the new version.
</documentation>
</annotation>
<complexType>
<choice maxOccurs="unbounded" minOccurs="0">
<element name="migration-handler">
<annotation>
<documentation>
The migration handler specifies the name of a class to be executed
while migrating the process instance.
</documentation>
</annotation>
<complexType>
<attribute name="class"/>
</complexType>
</element>
<element name="activity-mapping">
<annotation>
<documentation>
One activity mapping will be present for each activity of which the
name changed.
</documentation>
</annotation>
<complexType>
<attribute name="old-name" type="string" use="required">
<annotation>
<documentation>
Name of the activity in the previously deployed
process definition.
</documentation>
</annotation>
</attribute>
<attribute name="new-name" type="string" use="required">
<annotation>
<documentation>
Name of the activity in the newly deployed
process definition.
</documentation>
</annotation>
</attribute>
</complexType>
</element>
</choice>
<attribute default="migrate" name="action" type="tns:migrationActionType"/>
</complexType>
</element>
Attribute Detail
action
Type:
tns:migrationActionType
Use:
optional
Default:
"migrate"
Defined:
locally, within (this) tns:migrate-instances element
XML Source (see within schema source)
<attribute default="migrate" name="action" type="tns:migrationActionType"/>
Content Element Detail
tns:activity-mapping
Type:
anonymous, empty content
Defined:
locally, within (this) tns:migrate-instances element
One activity mapping will be present for each activity of which the name changed.
XML Source (see within schema source)
<element name="activity-mapping">
<annotation>
<documentation>
One activity mapping will be present for each activity of which the
name changed.
</documentation>
</annotation>
<complexType>
<attribute name="old-name" type="string" use="required">
<annotation>
<documentation>
Name of the activity in the previously deployed
process definition.
</documentation>
</annotation>
</attribute>
<attribute name="new-name" type="string" use="required">
<annotation>
<documentation>
Name of the activity in the newly deployed
process definition.
</documentation>
</annotation>
</attribute>
</complexType>
</element>
tns:migration-handler
Type:
anonymous, empty content
Defined:
locally, within (this) tns:migrate-instances element
The migration handler specifies the name of a class to be executed while migrating the process instance.
XML Source (see within schema source)
<element name="migration-handler">
<annotation>
<documentation>
The migration handler specifies the name of a class to be executed
while migrating the process instance.
</documentation>
</annotation>
<complexType>
<attribute name="class"/>
</complexType>
</element>
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/