Java NIO high-performance messaging (thousands of clients per CPU)
No
Yes
Real Time Messaging Protocol (RTMP)
No
Yes
Data throttling
No
Yes
Reliable communications
able to deploy my application directly from the workspace
bad news is that JBoss AS 7 does not currently support other persistence providers like Eclipselink, OpenJPA or DataNucleus
GlassFish and Resin, you can simply drop the JARs of your preferred provider and its dependencies in a designated folder of your server installation and edit your persistence.xml to override the default provider of the server
JBoss AS 7 appears to require an adapter per persistence provider, which to me looks like an unfortunate and unnecessary design decision
potential to take over the lead from GlassFish
documentation continues to be sketchy and far below the standard of JBoss AS 5
surprisingly lean and fast
top-level performance
classloader leaks
productivity issues of the Eclipse integration
lack of support for JPA providers other than Hibernate
Each of these is currently a blocker for using JBoss AS 7 in production
Redeployment
after a couple of redeployments, there was an OutOfMemoryError
new classloader leak
JBoss AS 7: Catching up with Java EE 6
Performance measurements
JBoss AS 7.0.2
GlassFish 3.1.1
Empty server startup time 1.9 s
3.2 s
Empty server heap memory 10.5 MB
26.5 MB
Empty server PermGen memory 36.3 MB
28.4 MB
MyApp deployment time 5.8 s
JBoss AS 7 is now at a competitive level with Resin and Glassfish and actually outperforms Glassfish in almost all of these tests
JSR-303 (“Bean Validation”) ActionScript3 framework for form validation
validation framework is a specific adaptation of the JSR-303 (Bean Validation) specification to Flex: like its Java counterpart, it relies on validation annotations placed on bean properties and provides an engine API that lets you validate your forms without writing by hand a specific validator for each of your input fields
code generation tools provided by GraniteDS so that when you write your Java entity bean with validation annotations, they are automatically replicated in your ActionScript3 beans
problem with LCDS is mainly that it promotes a strict “client / server” architecture, with – roughly speaking – a heavy Flex client application connected to a server almost reduced to a database frontend
big majority of these organizations use BlazeDS, a free and open-source subset of LCDS
need more advanced mechanisms than just Remoting start looking for open-source libraries to enable deeper integrations with the Java business layer, and GraniteDS is for sure the most popular project
“Flex Data Services” (now renamed to “Live Cycle Data Services”)