InfoQ

InfoQ

News

My Bookmarks

Login or Register to enable bookmarks for unlimited time.

The content has been bookmarked!

There was an error bookmarking this content! Please retry.

GraniteDS Continues to Evolve

Posted by Craig Wickesser on Jun 27, 2009

Sections
Process & Practices,
Development,
Operations & Infrastructure
Topics
Release ,
Rich Internet Apps ,
Java
Tags
Java EE ,
GraniteDS ,
Flex

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.

 

No comments

Watch Thread Reply

Educational Content

Jesper Boeg on Priming Kanban

In this interview, Jesper Boeg, author of the new InfoQ book – Priming Kanban, discusses the keys to using Kanban effectively, and how to get started if you are currently using other approaches.

New-age Transactional Systems - Not Your Grandpa's OLTP

John Hugg discusses high volume transaction processing applications with high and low frequency profiles, and how VoltDB can be used for that purpose.

Cool Code

Kevlin Henney examines code samples to see what can be learned from them starting from the premise that one won’t write great code unless he knows how to read it.

Collaboration: At the Extremities of Extreme

Jason Ayers share the observations he made watching a team of developers collaborating in real time on the same code base, pushing XP, pair programming and continuous integration to their extremes.

Yesod Web Framework

Michael Snoyman presents Yesod, a web framework written in Haskell and containing a web server, templating, ORM, libraries (templating, gravatar, etc.).

Transactions without Transactions

Richard Kreuter and Kyle Banker on how to avoid classical RDBMS transactional systems by using compensation mechanisms, transactional messaging or transactional procedures.

Attila Szegedi on JVM and GC Performance Tuning at Twitter

Attila Szegedi talks about performance tuning Java and Scala programs at Twitter: how to approach GC problems, the importance of asynchronous I/O, when to use MySQL/Cassandra/Redis, and much more.

10 tips on how to prevent business value risk

One category of risk that project teams need to ensure they address is business value failure – delivering a product that fails to provide value for the business investor.