[m2] J2EE and EJB3

[Richard Wallace <rw...@thewallacepack.net>]

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: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] J2EE and EJB3

[Stephane Nicoll <st...@gmail.com>]

On 11/9/05, Richard Wallace <rw...@thewallacepack.net> wrote:
>
> Just to be sure I'm understanding what I'm reading. The plugins for
> ejb3 and par artifacts are in the maven sandbox. To use them maven
> needs to support packaging types of ejb3 and par. Also, the ear plugin
> has to support artifacts of that type, which looks like it has been done
> in MNG-1264.


Yes, it has been done (ear plugin needs to be rebuild though).


Has the new lifecycle been committed in maven-core for par and ejb3?


No. I still need to request this. I don't have commit rights in this module.
As I said, stay tuned on MNG-699, I will add info as soon as things get
done. You can apply the lifecycle to a local copy and bootstrap if necessary

Cheers,
Stéphane

>
> Stephane Nicoll wrote:
> > On 11/9/05, Richard Wallace <rw...@thewallacepack.net> wrote:
> >
> > Are there plugins for building pars and ejb3 artifacts?
> >
> >
> >
> > Yes, in the sandbox. Watch out MNG-699.
> >
> > Cheers,
> > Stéphane
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>


--
.::You're welcome ::.

Re: [m2] J2EE and EJB3

[Richard Wallace <rw...@thewallacepack.net>]

Just to be sure I'm understanding what I'm reading.  The plugins for 
ejb3 and par artifacts are in the maven sandbox.  To use them maven 
needs to support packaging types of ejb3 and par.  Also, the ear plugin 
has to support artifacts of that type, which looks like it has been done 
in MNG-1264.

Has the new lifecycle been committed in maven-core for par and ejb3?  If 
I were to use a nightly build of m2 and grab the plugins from the 
sandbox would I be up and running?

Thanks,
Rich

Stephane Nicoll wrote:
> On 11/9/05, Richard Wallace <rw...@thewallacepack.net> wrote:
>
> Are there plugins for building pars and ejb3 artifacts?
>
>
>
> Yes, in the sandbox. Watch out MNG-699.
>
> Cheers,
> Stéphane
>
>   


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org

Re: [m2] J2EE and EJB3

[Stephane Nicoll <st...@gmail.com>]

On 11/9/05, Richard Wallace <rw...@thewallacepack.net> wrote:

Are there plugins for building pars and ejb3 artifacts?



Yes, in the sandbox. Watch out MNG-699.

Cheers,
Stéphane