Granite Data Services (GDS) is a free, open source (LGPL'd), alternative to Adobe® LiveCycle® (Flex™ 2+) Data Services for J2EE application servers (such as JBoss) or servlet containers (such as Tomcat or Jetty). It is not, however, a drop-in replacement: you won't be able to simply deploy a LiveCycle Data Services application into a Granite Data Services server without (minimal) modifications. The main goal of this project is to provide a framework for Flex 2+, EJB3, Spring, Seam, Guice and Pojo application development with full AMF3/RemoteObject benefits. GDS implements service factories required for: * EJB3 (Session Beans that return Entity Beans), * Seam (with Identity security & Conversation support), * Spring (with Acegi security & Entity Beans support), * Guice/Warp (with Entity Beans support), * Simple Java classes (aka POJO) interactions. Since the 1.0 version, Granite Data Services also provides a data push feature based on a Comet-like implementation with AMF3 data polling over HTTP (producer/consumer). GDS is designed to be lightweight, robust, fast and highly configurable. Granite Data Services (GDS) is a free, open source (LGPL'd), alternative to Adobe® LiveCycle® (Flex™ 2+) Data Services for J2EE application servers. It is not, however, a drop-in replacement: you won't be able to simply deploy a Flex 2 Data Services application into a Granite Data Services server without modifications. The main goal of this project is to provide a framework for Flex 2/EJB3/Spring/Pojo application development with full AMF3/RemoteObject benefits. GDS implements service factories required for: * EJB3 (Session Beans that return Entity Beans), * Spring (Acegi & Ejb3), * Simple Java classes (aka POJO) interactions. GDS is designed to be lightweight, robust, fast and highly configurable. While GDS is still in early development stage, you should be already able to use the current 0.4 version in non critical production environment. See more in documentation. Main Features (available or planned) GDS is in constant evolution and those features are only informative. * Full AMF3 support. See GDS AMF3 documentation. * EJB3 services with transparent externalization mechanism and lazy initialized ActionScript 3 beans (Entity Beans / Hibernate). See EJB3 Services and Externalizers and Lazy Initialization. * EJB3 Entity Bean to ActionScript 3 classes code generator. See AS3 Generation. * Spring services. See documentation on Spring Services. * POJO services (remote calls to simple Java classes that expose public methods). See Pojo Services. * (planned) Data push. A Comet-like implementation with AMF3 data polling over HTTP (event/listener based architecture). * (planned) Entity repository: a client side entity repository that ensures uniqueness (only one instance of each entity is present in the flash VM), weakness (only currently bound objects are kept in memory), and that acts as a services frontend (all server calls/events are managed by this central component). This will be loosely inspired by Cairngorm. * (planned) Seam integration: a reliable GDS/Seam integration with full scopes (at least conversation) support. * (planned) A set of Flex components suitable for complex data structures. Live GDS/EJB3 Demo View a live demo here. This very basic sample application uses a JBoss4/Hibernate/MySQL environment with this model: Person 1->n Contact n->1 Address n->1 Country You may view (user:user) and create/modify/delete (admin:admin) persons or contacts with this demo, and search for person's first or last name. After reviewing this sample application, you may download graniteds-ejb3-0.4.0.zip or browse SVN repository. Links Granite DS * Download (Sourceforge) * Documentation (0.4 release) * Forum (Yahoo Tech Groups) * Bug reporting (Jira) * SVN repository (Sourceforge) * Sourceforge Project * RIAForge Project Related Resources * Flex 2 * AMF3 Specification * JBoss * Hibernate * EJB3 Specification Related Projects * OpenAMF * Red5 * Amfphp * SabreAMF * Many others on OSFlash