Global Notes:
5.X products are parts of the “Blu Age II – Legacy to cloud” product family, built on Kepler (Eclipse 4.3);
Product documentation is available at http://wikimod.bluage.com/mediawiki/index.php/Main_Page;
Starting with version 5.0, a new license management has been introduced, requiring the use of a new License Server (shipped separately – see corresponding documentation for details);
5.X versions rely on the launch configurations mechanism introduced with the 4.X product series in replacement of the previous workflow mechanism. Migrating from the 3.X workflow to the 5.X launch configuration is described in a dedicated guide.
A new session management is in place. It allows the user to use server session with in a Single Page Application. In order to use the session the instance defined in the View must be stereotyped “ScopeSesssion”. Reading or assigning objects to the session is done in “EventAction” within the View. Since in JSON we can only pass one parameter, extra parameters are considered coming from Http Session.
Use cases coming from “EventAction” diagrams:
If the “Call Operation Action” has one parameter, the object in parameter will be assigned to the session.
If the “Call Operation Action” has multiple parameter all parameter corresponding to session object will be read from the session.
If the “Call Operation Action” has a stereotype “preload” the parameter will be read from the session.
Global Notes:
5.X products are parts of the “Blu Age II – Legacy to cloud” product family, built on Kepler (Eclipse 4.3);
Product documentation is available at http://wikimod.bluage.com/mediawiki/index.php/Main_Page;
Starting with version 5.0, a new license management has been introduced, requiring the use of a new License Server (shipped separately – see corresponding documentation for details);
5.X versions rely on the launch configurations mechanism introduced with the 4.X product series in replacement of the previous workflow mechanism. Migrating from the 3.X workflow to the 5.X launch configuration is described in a dedicated guide.
A new session management is in place. It allows the user to use server session with in a Single Page Application. In order to use the session the instance defined in the View must be stereotyped “ScopeSesssion”. Reading or assigning objects to the session is done in “EventAction” within the View. Since in JSON we can only pass one parameter, extra parameters are considered coming from Http Session.
Use cases coming from “EventAction” diagrams:
If the “Call Operation Action” has one parameter, the object in parameter will be assigned to the session.
If the “Call Operation Action” has multiple parameter all parameter corresponding to session object will be read from the session.
If the “Call Operation Action” has a stereotype “preload” the parameter will be read from the session.
List of issues fixed:
