Group items tagged

this externalizer may be used with any POJO bean.

 ActionScript 3 Reflection API

describeType

method returns

public class ClassHolderDTO<T> {    private Class<T> classToTransfer;// get/set boilerplate}

Resource

Class<Resource> entityClass

The configuration of a GraniteDS project will generally involve the following steps : Add the GraniteDS jars to the WEB-INF/lib folder of the WAR file or the lib folder of the EAR file Add the GraniteDS listener, servlets and filters in the standard WEB-INF/web.xml configuration file Define the internal configuration of GraniteDS in the WEB-INF/granite/granite-config.xml file Define the application configuration of GraniteDS (remoting destinations, messaging topics...) in the WEB-INF/flex/services-config.xml

You will always need granite.jar

jar for your JPA provider (granite-hibernate.jar for Hibernate)

GDS/Tide project represents the Data Services part of GDS

comparable to LiveCycle Data Services, which is neither open source nor free, as it provides similar features such as client container of managed entities, data paging, and integration with server components, but it is based on completely different principles:

strongly typed Hibernate/JPA detached objects

Granite Data Services provides a messaging feature, code name Gravity, implemented as a Comet-like service with AMF3 data polling over HTTP (producer/consumer based architecture)

GraniteDS messaging relies on two main AS3 components on the Flex side: org.granite.gravity.Consumer and org.granite.gravity.Producer

6.3. Common Configuration There are three main steps to configure Gravity in an application: Declare the Gravity servlet implementation for your target server in web.xml Declare a messaging service and destination in services-config.xml, mapped to a specific channel definition of type GravityChannel

10.3.5. Security GraniteDS provides a client-side component named identity that ensures the integration between the client RemoteObject credentials and the server-side container security. It additionally includes an easy-to-use API to define runtime authorization checks on the Flex UI.

CDI identity component (of class org.granite.tide.cdi.Identity) predictably provides two methods login() and logout()

identity component is integrated with server-side role-based security and can be used to get information or show/hide UI depending on the user access rights:

16.2. Writing a Security Service

login(Object credentials)

authorize(AbstractSecurityContext context)