|
From: Colin S. <col...@ex...> - 2005-11-26 17:33:37
|
The 'ejbtest' integration test sample in autobuilds had been broken by developments in recent months (in the Spring codebase, mainly jars and the like moved around), without me or anybody else picking this up. I've gone through and fixed the sample so it works again. Originally this sample had been tested with JBoss 3.2. I've made it work with JBoss 4.0.2 and 4.0.3SP1, which required some rework of the local EJB handling, as JBoss 4.0 is more compliant with the (EJB 2.1) spec and no longer binds local bean homes in a globally known JNDI location, where the sample was trying to use them from. Instead, they must be accessed only via the Environmental Naming Context (ENC) JNDI tree, which required adding <ejb-local-ref> elements in the web.xml or ejb.xml files of components that need to access them. More EJB XML, ughh! Anyway, it's working now. I will at some point relatively soon try to go into this app again to make sure it works with WebLogic and WebSphere too. One issue is that right now it relies on a unified classloader being used for all jars and ejbs loaded at the ear (applicaiton.xml) level. This is probably not the default in WebLogic and WebSphere. Colin |