Java frameworks
A software framework is a reusable design for a software system (or subsystem). This is expressed as a set of abstract classes and the way their instances collaborate for a specific type of software. Software frameworks can be object-oriented designs. Although designs don't have to be implemented in an object-oriented language, they usually are and in some ways they can be considered the object-oriented equivalent of software libraries. A software framework may include support programs, code libraries, a scripting language, or other software to help develop and glue together the different components of a software project. Various parts of the framework may be exposed through an application programming interface (API).
From : http://en.wikipedia.org/wiki/Software_framework
Granite Data Services
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.
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.
Loading .....