Group items matching

in title, tags, annotations or url

free and more feature rich alternative to BlazeDS, but also outranks LCDS’ out-of-the-box features when it comes to data management, streaming media and integrating with mobile devices and Cloud computing

developer tools like code generation, invocation test drive and interoperability with multiple IDEs and frameworks

supporting integration with mobile clients (Android, Windows Phone 7, RIM Playbook and soon iOS) and the Java service layer, which includes support for Java POJOs, EJBs, Spring Beans, Grails controllers, Hibernate Objects and XML Web Services

JBoss AS Tools

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

documentation continues to be sketchy and far below the standard of JBoss AS 5

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

@RunWith(Arquillian.class)

JDBC Templates hardly give any abstraction on top of the database and you’re on your own for Object Relational Mapping. We strongly advise to use JPA wherever possible; it gives portability by abstracting most of the database specific SQL that you would need, and it does all the hard and painful work of object mapping

small part of your application

cdiqi just forces Quartz to use CDI beans as its jobs

bounds request context to every job execution so that it's possible to use @RequestScoped, @Dependent and @ApplicationScoped jobs and especially beans

jboss.as.jpa.adapterModule

jboss.as.jpa.adapterClass

org.jboss.as.jpa.hibernate3.HibernatePersistenceProviderAdaptor

Working with other persistence providers

A project to build integration for persistence providers like EclipseLink, is here.

Troubleshooting

“org.jboss.as.jpa” logging can be enabled to get the following information: INFO - when persistence.xml has been parsed, starting of persistence unit service (per deployed persistence.xml), stopping of persistence unit service DEBUG - informs about entity managers being injected, creating/reusing transaction scoped entity manager for active transaction TRACE - shows how long each entity manager operation took in milliseconds, application searches for a persistence unit, parsing of persistence.xml

To enable TRACE, open the as/standalone/configuration/standalone.xml (or as/domain/configuration/domain.xml) file. Search for <subsystem xmlns="urn:jboss:domain:logging:1.0"> and add the org.jboss.as.jpa category

Packaging the Hibernate 3.5 or greater 3.x JPA persistence provider with your application

jboss.as.jpa.providerModule needs to be set to hibernate3-bundled.

<property name="jboss.as.jpa.providerModule" value="hibernate3-bundled" />

Sharing the Hibernate 3.5 or greater JPA persistence provider between multiple applications

Applications can share the same Hibernate3 (for Hibernate 3.5 or greater) persistence provider by manually creating an org.hibernate:3 module (in the AS/modules folder). Steps to create the Hibernate3 module:

<property name="jboss.as.jpa.providerModule" value="org.hibernate:3" />

consideration of the system as a whole

return a row

3 ways to do this

EntityManger.find()

returns a typed instance of the entity when it is found, null when it is not found

But what if the row isn’t in the database (anymore)?

We get an unchecked exception: NoResultException

We never know for sure what we can expect from our database, so throwing an unchecked exception seems the wrong choice for this use-case

Corporate - central Wiki

Build Server (Continuous Integration)

Testing (tools and practices)

Code Coverage

Services, practices & tools that should exist in any software development house, part 1