JPA applications that create an EntityManagerFactory on their own, either using the PersistenceProvider SPI directly or through an intermediary mechanism such as Spring's LocalContainerEntityManagerFactoryBean
standard Java EE-applications may ignore the provider implementation and rely on the standard features provided by the container - JBoss AS7 supporting standard JPA 1.0 and 2.0
future versions of JBoss AS7 it will be possible to use alternative persistence provider implementations
use the granite-hibernate4.jar instead of granite-hibernate.jar
Flex 4.5 broke a few APIs and there were two main issues with Tide :
The client libraries crashed when run in a mobile application
The PagedQuery was unusable
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
could either be
automatically detected from the server configuration, or could
be configured by the user through the
useUnicode and
characterEncoding properties
character encoding between client and server is
automatically detected upon connection
character_set_server for server
versions 4.1.0 and newer
To override the automatically detected encoding on the client
side, use the characterEncoding property
in the URL used to connect to the server.
just stumbled across an important link to 'developer guide' docs on this page, which isn't referenced anywhere from the main documentation page! (http://www.graniteds.org/confluence/display/DOC)