geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kanchana Welagedara" <>
Subject Re: classpath for MDBs
Date Thu, 27 Jul 2006 05:16:04 GMT
Hi Nathan

Since you are using openejb.jar why don't you package the service as a "
jar" rather than ear?
Following are the deployment plans for Geronimo

 File Standard Deployment Descriptors in the J2EE specification Apache
Geronimo specific Deployment plan  Web Application Archive (WAR)
web.xmlunder the WEB-INF directory
geronimo-web.xml  Enterprise Web application archive (EAR) application.xml
geronimo-application.xml  J2EE Connector resources archive (RAR) ra.xml
geronimo-ra.xml  J2EE client application archive (JAR) client.xml
geronimo-application-client.xml  JAR containing EJBs ejb-jar.xml under the
META-INF directory openejb-jar.xml

 Developers are  working on the deployment plans for the geronimov1.1
yet.Itwill be on line
soon.I'm giving you the following resource url to get you an understanding
of how to deploy JMS and MDB with Geronimo .Have a  look in this  article

The Article has been provided you all the artifacts in geronimov1.0 version
you can use the geronimo_home/bin/upgrade Tool to generate the deployment
plan for the GeronimoV1.1
Hope this is useful for you

On 7/27/06, Nathan Mittler <> wrote:
> Hi,
> I'm fairly new to EJB and am trying understand the way classpaths work in
> Geronimo with respect to MDBs.  I have a pretty simple app - just one MDB
> that consumes from JMS and writes to the database.  It requires a few jars
> (hibernate, spring, etc) and I bundle those dependencies along with the MDB
> into an ear (using Maven) and then deploy the whole app to Geronimo 1.1.
> However, when the MDB receives JMS messages from AMQ, it doesn't seem to
> be able to find any of the other classes in the EAR.  I'm guessing this is
> due to it being in the classloader of the AMQ connector, rather than the ear
> upon invocation.  I was able to fix this by manually adding all of the
> dependencies to Geronimo's repository and then listing those dependencies in
> the openejb-jar.xml.  This seems to do the trick.
> My questions are:
> 1) Is there a better way to deploy a module along with all its
> dependencies to Geronimo - rather than wrapping them up in an ear?  A tool
> perhaps?
> 2) Is there a more appropriate (and simpler) solution to the classloader
> "problem" with MDBs? ( ... assuming I have diagnosed the problem correctly)
> Thanks,
> Nathan Mittler

View raw message