I want to start playing with JBoss and EJB3 and I'm trying to decide on
the best way to structure the project. Based on what I've read about it
I think the following is what seems to make the most sense to me and I'm
wondering what everyone else's opinions are.
With EJB3 you have a .ear file that is composed of a .par file, a .ejb3
file, and a .war file. So, I'm thinking of doing a multi-module project
with a module for each of those, so the structure would look like:
myj2eeapp/
myj2eeapp-par/
myj2eeapp-ejb3/
myj2eeapp-war/
myj2eeapp-ear/
The myj2eeapp would just be packaged as a pom.
myj2eeapp-par would create the par artifact, which is just a jar with a
persistence.xml file in the META-INF directory.
myj2eeapp-ejb3 would create the ejb3 file, which is just a renamed jar
file - nothing special is added to them. I see that there is an ejb
plugin for maven already, could this be used for ejb3 as well?
myj2eeapp-war would of course be packaged as a war, so that's simple enough.
myj2eeapp-ear would create and deploy the ear artifact, so it would have
dependencies on the other 3 modules of the project.
Are there plugins for building pars and ejb3 artifacts? Does this seem
reasonable or is there a better way of structuring the project?
Thanks,
Rich
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
