Migrating from Designer Versions Prior to 9.0

ActiveVOS Designer User’s Guide

Previous | Next

Migrating from Designer Versions Prior to 9.0

There are a few changes to be aware of for new versions of ActiveVOS Designer.

Existing BPEL processes have an associated visual layout file that includes all layout and annotation information (.vbpel files). New BPEL files contain this information, eliminating the vbpel file and making it easier to move BPEL files to another location without losing annotations. To delete the vbpel file for existing processes, open and save your older processes. This is not required. This feature does not apply to BPEL 1.1 processes or processes designed in the Classic style.
The Process Editor palette offers a choice of BPMN-Centric (the default) or the existing BPEL-Centric stylesheet. Existing processes can be opened with either stylesheet with the exact same results. To use the BPEL-Centric palette, change the Layout Preference.
You can add an XQuery nature to existing projects to take advantage of the XQuery editing and runtime tools. Right-mouse click on a project and select Add XQuery Nature.
POJO (and XQuery) custom functions can be listed in the Expression Builder and deployed in your deployment contribution. There is no longer any function context set up required for new POJO custom functions.
If you have existing XQuery functions, be sure to read the Release Notes for possible changes you may need to make to your functions.
A newly generated b-unit ant script contains targets and parameters for code coverage. You can manually add these ant tasks to your existing b-unit ant scripts. You can also add XQuery modules as b-unit resources.
You can migrate running process instances to run against a new process version. As a first step, open your existing process, modify it slightly by moving an activity a bit (mark the process as dirty), and save the process without making any other changes. Update the PDD to enable the Migrate Version option. Then deploy the contribution, which contains the unchanged process structure and updated PDD. After you have deployed the Version 9 contribution, you can then make structural changes to your process and migrate running process instances to the new version.
Version 9 uses a newer version of the Saxon XSL parser, which does not support the undocumented and non-standard @value attribute for the <xsl:param> element. If your older b-unit tests or other XSL functions contained this attribute, they will not be able to be parsed by Saxon. To correct this problem, use an expression such as select= instead of value=.