1.2 Change History

1.2.1  Version 2.1.x, May 2009

The main amendments of this version provide support for Unix, both for development and as a deployment environment.

1. Support for Unix users
   • The Eclipse plugin has been tested on Ubuntu 9.0.4.
   • Fixes to Eclipse plugin to support Unix style directories in the GigaSystemBuilder preferences.
   • GigaSystemBuilder now supports the Unix deployment target in the DeploymentOption.
   • Fixes to allow code generation within Unix environment.
2. New scripts generated to support Unix deployments.
   • startGSC.sh script to start the appropriate number of GSCs.
   • startGSC.sh script to start the GSM.
   • "deployApp.sh" script to copy and deploy the appropriate jars to the GigaSpaces environment.
   • "deployApp.sh shutdown" - shutdown sub-command of deployApp script, to kill all the previously started GigaSpaces processes.

1.2.2  Version 2.1.0, April 2009

• Updated GigaSystemBuilder tutorial and images.
• Small changes to documentation.
• Minor fixes to examples.

1.2.3  Version 2.0, March 2009

The main theme of this version is to support larger applications of GigaSpaces, with more services and PUs, interrelated initialisation, and automation of various deployments.

1. Support for building services
   • Service method attributes to define (a) routing styles and (b) single- or multi-processing.
   • Space-based Collections - SpaceHashMap and SpaceDelayQueue - which provide Java collections that are automatically backed up by being written to a space.
   • First-class objects for modelling message handling - subscriber, receiver and browser.
   • Support for coordinated application start-up across bean init-methods, PU and space start-up, PU initialisation calls and pulses (timed triggers). The inter-PU initialisation calls are modelled using Spring beans scripting. This allows for interdependent beans to start up in a coordinate fashion.
2. Support for building applications
   • A new start wrapper around the Client's implementation, to automatically delay the implementation during startup
   • A modelled 'pulse' object to support test feeders and periodic health checks.
3. Core Foundation framework services
   • A common library for proxies to spaces and services that avoids the dependencies of pu.xml deployment.
   • A Utilities library class.
   • Generation of a foundation Processing Unit (PU) that handles startup of interdependent services and processing units
   • A key generation service, which provides a consistent primary-key generation function for the grid, and also demonstrates the use of the other infrastructure features in version 2 of GigaSystemsBuilder.
4. Deployment
   • Named deployments, with different numbers of PUs, backups, types of machine etc. in the different deployments.
   • Specification of depoyments for the whole application, but with overrides for specific Processing Units
   • Deployment to Cloud and Windows CLI (Command-Line Interface). IDE-style debugging is support with deployment to Eclipse. (This feature was in Version 1.)