Granite Data Services 1.2.0 GA (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Granite Data Services 1.2.0 GA (Default branch)
# 1  
Old 01-08-2009
Granite Data Services 1.2.0 GA (Default branch)

Granite Data Services (GDS) is an alternative to Adobe LiveCycle (Flex 2) Data Services for J2EE application servers. The primary goal of this project is to provide a framework for Flex 2+/EJB3/Seam/Spring/Guice/Pojo application development with full AMF3/RemoteObject benefits. It also features a Comet-like Data Push implementation (AMF3 requests sent over HTTP) and ActionScript3 code generation tools (Ant task and Eclipse Builder). License: GNU Lesser General Public License (LGPL) Changes:
The Gravity implementation for Tomcat was completely rewritten. JBossWeb, a modified Tomcat included in JBoss 5.0.0 GA, is supported. TopLink and EclipseLink were integrated. A specific security service was added for GlassFish. Seam 2.1 in Tide is supported. Tide for Spring and Tide for EJB improvements were made. The WebCompiler now includes the Flex 3.2 SDK and is able to compile code for Flash 10. Maven artifacts are now available on java.net. Image

Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread
Login or Register to Ask a Question
Apache::Session::Flex(3pm)				User Contributed Perl Documentation				Apache::Session::Flex(3pm)

NAME
Apache::Session::Flex - Specify everything at runtime SYNOPSIS
use Apache::Session::Flex; tie %hash, 'Apache::Session::Flex', $id, { Store => 'DB_File', Lock => 'Null', Generate => 'MD5', Serialize => 'Storable' }; # or tie %hash, 'Apache::Session::Flex', $id, { Store => 'Postgres', Lock => 'Null', Generate => 'MD5', Serialize => 'Base64' }; # you decide! DESCRIPTION
This module is an implementation of Apache::Session. Unlike other implementations, it allows you to specify the backing store, locking scheme, ID generator, and data serializer at runtime. You do this by passing arguments in the usual Apache::Session style (see SYNOPSIS). You may use any of the modules included in this distribution, or a module of your own making. If you wish to use a module of your own making, you should make sure that it is available under the Apache::Session package namespace. USAGE
You pass the modules you want to use as arguments to the constructor. The Apache::Session::Whatever part is appended for you: you should not supply it. For example, if you wanted to use MySQL as the backing store, you should give the argument "Store =" 'MySQL'>, and not "Store =" 'Apache::Session::Store::MySQL'>. There are four modules that you need to specify. Store is the backing store to use. Lock is the locking scheme. Generate is the ID generation module. Serialize is the data serialization module. There are many modules included in this distribution. For each role, they are: Store: MySQL Postgres DB_File File Lock: Null MySQL Semaphore Generate: MD5 Serialize: Storable Base64 UUEncode In addition to the arguments needed by this module, you must provide whatever arguments are expected by the backing store and lock manager that you are using. Please see the documentation for those modules. AUTHOR
This module was written by Jeffrey William Baker <jwbaker@acm.org>. SEE ALSO
Apache::Session::File, Apache::Session::DB_File, Apache::Session::MySQL, Apache::Session::Postgres, Apache::Session perl v5.10.1 2010-10-18 Apache::Session::Flex(3pm)