J2EE 1.4 Compliance in JBoss 4.0.3SP1

This JBoss documentation details the switches to flip to get proper J2EE 1.4 compliance. These couple changes and ensuring remote ejb-ref mappings (jnp://localhost:1099/blog/BlogService) in jboss-web.xml allows my relatively straight-forward application to run.

I deploy my EJBs in a jar, and the web-tier in a war. The war contains the client.jar for the EJBs as one would expect from a normal app server. This caused JBoss to complain of " Invalid invocation, check your deployment packaging" until I got the server configuration right.

I wonder if I could put together a nice script to customize these things for me in every new JBoss build.

Along the way, I also discovered that I had my datasource type mapping declared in my xdoclet call (in build.xml). This overrode my deployed datasource's "PostgreSQL 8.0" with just "PostgreSQL". That took a moment to figure out. Updating my JBoss version to "4.0" in xdoclet allowed me to drop the datasource type from the descriptors completely, and the server used the right mapping after that.

Filed Under: Computers Java Technology Blog-Code Linux