Hi all,

Granite Data Services 1.1.0 Release Candidate 3 is out. You may download it, as usual, on Sourceforge here.

This new release is actually a true release candidate since we have now reached a real feature freeze... Beside several bugfixes, this release comes with a huge Tide improvement and (again) an almost complete rewrite of gas3.

Tide specific new features (more informations will be soon available in GDS blog):

1. Full support of Seam events (both synchronously and asynchronously) via Gravity (data pushing).
2. Deeper integration with the Seam Query component and support for paged collections (you may bind a Seam Query to a DataGrid that will load collection items on demand).
3. Transparent initialization of lazy loaded collections.

Gas3 refactoring:

1. I had to rewrite again Gas3 in order to make easier the development of an Eclipse Builder (not yet available) and future extensions (different kind of inputs, such as some configuration XML files, in order to generate ActionScript3 code). The GDS Eclipse builder will mainly give automatic as3 generation features: when a Java class, in the scope of the generator, is created/modified/(re)moved, the builder will update automatically and accordingly as3 classes.
2. There is no changes for the average user but, if you have written a custom "controller", you should now write a custom "transformer"...

Here is the complete release note for this RC2 (see also GDS Jira):

New Features

• [GDS-117] - Tide: as3 client exception handlers
• [GDS-119] - Tide: Management of Seam events synchronous & asynchronous with Gravity
• [GDS-120] - Tide: Deeper integration with Seam Query framework component and support for paged collections
• [GDS-139] - Tide: implement automatic lazy loading of collections

Improvements

• [GDS-125] - tide.seam.Context expects type Seam in constructor, which is not necessary
• [GDS-135] - Integrate Tide managed entities with LCDS [Managed] annotation to simplify the gas3 templates
• [GDS-137] - Tide: implement merging of maps in Context
• [GDS-138] - Refactor Gas3 for Granite Eclipse Builder and future extendability
• [GDS-140] - Tide: Filtering of target components

Tasks

• [GDS-115] - Use mx.logging instead of trace in all as3 components

Bugfixes

• [GDS-116] - Tide: Incorrect destruction of finished conversation contexts
• [GDS-118] - Tide: NaN numbers incorrectly managed in context merge
• [GDS-122] - Authentication doesn't work with Gravity
• [GDS-124] - Typo in bean.gsp (interfaceProperties instead of interfacesProperties)
• [GDS-126] - Tide: Merge of collections in context loses order
• [GDS-127] - Improved saving of entity values before sending to server
• [GDS-128] - Tide: request wrapper not correctly cleaned during consecutive messages in the same http request
• [GDS-129] - Tide: Asynchronous impl depends on deprecated Seam 2.0.0 API
• [GDS-130] - Tide: remove messages dependency on JSF FacesContext/Locale
• [GDS-131] - Tide: missing update of id for new entities
• [GDS-132] - Error when deserializing RemotingMessage
• [GDS-133] - DefaultMethodMatcher does not find some methods with complex generic types
• [GDS-134] - Stateful session beans are cached in application context (should be in session cache)
• [GDS-136] - Incorrect management of context variables in conversation scope

Please note that documentation is (still and again) not yet ready but you may have a look at a work in progress here.

Best regards,
Franck.