J2EE projects layout

[BRUNOT Sébastien <se...@cegetel.fr>]

Hy,

I have a question regarding the maven J2EE project layout proposed by
vincent massol, that is :

ROOT\
    \applications
        \myEAR
    \modules
        \myAPI
        \myEJB
        \myWAR
    \containers
        \myJ2EEContainer
    \nodes
        \myDatabase
        \myHost

Suppose i have a .properties file associated with myWAR, but that i want
this .properties file to be deployed outside the WAR, under a directory
specified by the guys who rules exploitation... How do you achieve this ? By
storing the .properties file under ROOT\modules\myWAR\src\conf and building
two artifacts for myWAR (the war and the .properties file, or the war and a
zip file which contains the .properties file, etc...) ? Or by storing the
.properties file under another project (myHost ? ... ?).

Thanks for your help !

Sebastien Brunot

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

RE: J2EE projects layout

[Vincent Massol <vm...@pivolis.com>]

Hi Sebastien,

Here's what I do:

- If the config file is supposed to be packaged in the jar/war/rar/etc,
then I store it in the src tree of that jar/war/rar/etc

- if the config file is supposed to be tuned for production, i.e. it has
to be visible by the production guys for example, then I consider this
file a config file of the whole application in the container. I put it
in the container project. 

Maybe what you find misleading are the names:
- the "applications" projects are not the application per see (an
application is really an EAR deployed in a container and properly
configured)
- the "container" project really represent the executable application.
For example if you were developing a native executable C application,
you would write the code instead of the container and that would clearly
be your application. It's the same here.

If you have better name, please feel free to propose them as I'm not too
happy about them ;-)

Thanks
-Vincent

> -----Original Message-----
> From: BRUNOT Sébastien
[mailto:sebastien.brunot.prestataire@cegetel.fr]
> Sent: 16 September 2003 14:42
> To: 'Vincent Massol'
> Cc: 'users@maven.apache.org'
> Subject: J2EE projects layout
> 
> Hy,
> 
> I have a question regarding the maven J2EE project layout proposed by
> vincent massol, that is :
> 
> ROOT\
>     \applications
>         \myEAR
>     \modules
>         \myAPI
>         \myEJB
>         \myWAR
>     \containers
>         \myJ2EEContainer
>     \nodes
>         \myDatabase
>         \myHost
> 
> Suppose i have a .properties file associated with myWAR, but that i
want
> this .properties file to be deployed outside the WAR, under a
directory
> specified by the guys who rules exploitation... How do you achieve
this ?
> By
> storing the .properties file under ROOT\modules\myWAR\src\conf and
> building
> two artifacts for myWAR (the war and the .properties file, or the war
and
> a
> zip file which contains the .properties file, etc...) ? Or by storing
the
> .properties file under another project (myHost ? ... ?).
> 
> Thanks for your help !
> 
> Sebastien Brunot


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