Your opinion matters! Please fill in the InfoQ Survey!

GraniteDS Continues to Evolve

| by Craig Wickesser Follow 0 Followers on Jun 27, 2009. Estimated reading time: 1 minute |

A note to our readers: As per your request we have developed a set of features that allow you to reduce the noise, while not losing sight of anything that is important. Get email and web notifications by choosing the topics you are interested in.

GraniteDS 2.0.0, a free and open-source alternative to LiveCycle/BlazeDS, was released earlier this week.  It boasts a significant set of new features and restructuring.  Some of the new features include:

  • Persistence Support
    • OpenJPA
    • DataNucleus/JPOX
  • Application Servers Support
    • GlassFish v3
    • WebLogic 10
    • Google App Engine
  • OSGi Support
    • POJOs only
  • Spring Security Support

The Tide framework has also been enhanced, Franck Wolff, project founder, had this to say about the enhancements,

The GraniteDS "Tide" framework is now mature and brings on the Flex side several mechanisms inspired by JBoss/Seam: events and observers, injections and outjections, contexts, sub-contexts and managed beans. You may now design your Flex application using the same kind of architecture you were used to follow in the web-tier in classical JSF applications. The integration with the Seam framework is complete, so you may really create a Flex frontend to your existing JSF/Seam application without changing anything to your server code.

One of the other major changes was in the repackaging and restructuring of the entire source code. If you're using 1.x releases of GraniteDS you'll need to take a few steps to migrate over to the 2.0.0 release. The details are explained in the post "Migration Notes for GraniteDS 2.0 beta 1".

The GraniteDS team is hard at work on the 2.1.0 release which is expected to include a subset of the JBoss/Seam features for the Spring and EJB3 frameworks.  The ultimate goal is to provide a solution in which Tide can be used on the Flex side without worrying about the server framework (Seam, Spring or EJB3).  Lastly, if the specification and implementations for Web Beans (JSR-299) is available you can expect integration support to be provided as well.


Rate this Article

Adoption Stage

Hello stranger!

You need to Register an InfoQ account or or login to post comments. But there's so much more behind being registered.

Get the most out of the InfoQ experience.

Tell us what you think

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread
Community comments

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread

Allowed html: a,b,br,blockquote,i,li,pre,u,ul,p

Email me replies to any of my messages in this thread


Login to InfoQ to interact with what matters most to you.

Recover your password...


Follow your favorite topics and editors

Quick overview of most important highlights in the industry and on the site.


More signal, less noise

Build your own feed by choosing topics you want to read about and editors you want to hear from.


Stay up-to-date

Set up your notifications and don't miss out on content that matters to you