ASTRO Suite 3.4 - RELEASE NOTES
Contents
What's New
The ASTRO Suite 3.4 is a major release of the ASTRO Suite that adds some functionalities, fixes some bugs and addresses some usability issue.
The tools of the ASTRO Suite that are based on Java have been compiled and tested using Java 5. From this version the JRE 1.5 will be the only officially supported version of the Java virtual machine.
wsToolset
- Dependencies
- Java 1.5 compliance
- Features
- Added the support for the bpel xpath expression "getVariableData(a,b)" where "a" is the name of the variable and "b" the name of the part
- Added the relative path support for bpel, wsdl and function files referenced inside the requirements defininition file
- Handling of the break bpel activity inside the while bpel activity
- Added the support for the datanet processes monitor
wsMonitor
- Dependencies
- Java 1.5 compliance
wsUseCases
- Features
- wsUseCases has been trasformed into an Eclipse plug-in that allows for easy import of Astro Demo use cases into the Eclipse workspace
wsChainManager
- Dependencies
- Java 1.5 compliance
- Requires Eclipse 3.2.2
- Removed dependencies from ant for deployment in the composition task
- Features
- Disabled transaction management generation
- Disabled presentation aspect generation
- Removed some options from console (verbosity, sts, path-view)
- Usability
- The plugin no longer needs to be configured prior to usage (you may still want to change something in the configuration.properties file at your own risk); the CATALINA_HOME and the TMP folders location for the application are set grabbing the values from the relevant enviroment variables
- The plugin shows examples and counterexamples of the verification task within the default browser
- The user can startup and shutdown the Tomcat server via a console button
- The plugin actions are enabled selecting a wsRequirement Definition file (.chor); this files will be used to performs the tasks
- The execution of the chain commands is stopped if one of the steps fails
- Bug Fixes
- Fixed the radio buttons behaviour to specify the type of translation (DN|KL|GL)
wsRequirement
- Features
- Java 1.5 compliance
- Requires GMF 1.0.3 runtime
- Invalid datanet and datanet_diagram files are automatically recreated when opening valid chor files
- Usability
- Implemented support for relative paths within wsRequirement Definition file
- Added a brand new Astro Suite wsRequirement perspective
- Added Preferences menu for the wsRequirement plugins to the Eclipse environment (mainly due to allow for anti-aliasing enabling/disabling)
- Datanet is displayed using a left-to-right layout
- Labels are anchored to the relevant nodes rather than appearing inside them
- Review of the editor's icons and palette
- InputNode and OutputNode are associated only to semantically valid messages appearing within the 'partnerLinkType', 'myRole' and 'partnerRole' elements of BPEL and WSDL files
- Bug Fixes
- Fixed the GTK anti-aliasing bug under Debian and Ubuntu Linux flavours
- Fixed a bug that saved the wsRequirement Defition File (.chor) immediately after the opening of the editor
- Fixed a bug that caused the crash of the Data Flow tab if the datanet files were corrupted; now these files are rebuild using the info contained within the .chor file
- Fix a bug that created an invalid chor file for 'datareqs' whose number of nodes was greater than three
- Fixed a bug in the handling of the selection event within the property view
wsAnimator
- Dependencies
- Java 1.5 compliance
- Requires Eclipse 3.2.2
- Bug Fixes
- Fixed the bug that caused the plug-in to crash if the animation was repetead
Last Update: 29 June 2007
