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:

9.2.6. Integration with Seam Security

When not using the Seam native setup, you have to manually configure the integration of Seam Security in granite-config.xml.

<granite-config>    ...    <!--     ! Use Seam 2.1+ based security service.     !-->     <security type="org.granite.seam21.security.Seam21SecurityService"/> </granite-config>

15.6. Authorization

Seam Security is built around the premise of users being granted roles and/or permissions, allowing them to perform operations that may not otherwise be permissible for users without the necessary security privileges

15.6.1. Core concepts

@Secured @NamedResource("contact")

Interceptors will be ignored by CDI container unless it is listed in beans.xml

Using Apache Shiro Security to allow login via Facebook – part 1

how you create a JDBC realm

Apache Shiro

 doGetAuthenticationInfo(AuthenticationToken token) 

previously known as the JSecurity project

The word Subject is a security term that basically means "the currently executing user"

Core Concepts: Subject, SecurityManager, and Realms

ComparisonThis section provides a brief comparison of SAFs functionality with that of the Acegi Security Framework [11] and JBoss Seam Security [12]

Acegi’s Policy Decision functionality is not based on Java security standards but on a proprietary solution

ACL defines per domain object who has access permissions

adding this profile to your settings.xml

Seam 3 modules and examples are published to the JBoss Community Maven Repository when they are released

<url>http://repository.jboss.org/nexus/content/groups/public</url>

In order to initialize GDS/Tide for CDI and Hibernate, you must add granite.jar, granite-hibernate.jar and granite-cdi.jar to your WEB-INF/lib

The easiest way to add GraniteDS support to a CDI project in a Servlet 3 compliant container (currently only GlassFish v3) is by adding a configuration class in your project. This class will be scanned by the servlet 3 container and GraniteDS will use the annotation parameters to determine the application configuration

GraniteConfig.java import org.granite.config.servlet3.FlexFilter; import org.granite.gravity.config.AbstractMessagingDestination; import org.granite.gravity.config.servlet3.MessagingDestination; import org.granite.tide.cdi.CDIServiceFactory; import org.granite.tide.cdi.Identity; @FlexFilter( tide=true, type="cdi", factoryClass=CDIServiceFactory.class, tideInterfaces={Identity.class} ) public class GraniteConfig { }

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)