Home | News | FAQ | Download | Lists | Issues | ||||||||||
IntroductionThe basic idea of this approach is that your Servlets and EJBs are together in your war file as one app.
How is this done? The support for running your EJBs (OpenEJB) is loaded into your webapp classloader and not visible to any other webapps. Not quite J2EEThis is very different than J2EE as defined by the spec as there aren't several levels of separation and heirarchy. This is going to take some getting used to and it should be understood that this style of packaging isn't J2EE compliant. J2EE classloading rules:
To pull that off, J2EE has to kill you on packaging:
Critically speaking, forcing more than one classloader on an application is where J2EE "jumps the shark" for a large majority of people's needs. SetupThis is new feature for OpenEJB 1.0. Configure OpenEJB per webapp requires the following steps:
Should you define other OpenEJB configuration settings use another <init-param> stanza. It's just for that. These parameters are directly passed to OpenEJB at initialization of the servlet. Think about the loader servlet as a bridge between OpenEJB's world (EJBs) and Tomcat's world (servlets, JSPs). At startup OpenEJB prints out all of the configuration settings to Tomcat logs: INFO: Installing web application at context path /openejb from URL file:C:\webapps\openejb OpenEJB init-params: param-name: openejb.home, param-value: c:\openejb param-name: openejb.configuration, param-value: conf\openejb.cfg param-name: openejb.base, param-value: c:\webapps\openejb\WEB-INF\openejb param-name: openejb.loader, param-value: tomcat-webapp
|
||||||||||
|