Modular packaging of a large application

[Brian Styles <gi...@hotmail.com>]

Hi everyone,

I've built an application in a standard j2EE format

JSPs-->Struts-->Session Beans-->CMR Entity Beans.

This is deployed in an exploded ear, with struts and JSPs in the war as well 
as the session bean interfaces. Then I have the Session Beans and CMR Entity 
Beans in a jar.

Now I want to go to a larger environment where different developers are 
working on different modules, yet I still want each module to be accessable 
through a single point - ie, struts.

Struts 1.1 has the concept of modules, allowing different struts config 
files per module, however, from the context of deployment I have some 
worries.

1) Should all my entity beans be packaged in a single jar?

2) Different modules will probably mean different session beans, jsps and 
struts actions.

Therefore, I would really appreciate advice/experienc on packaging up an 
architecture like this.

regards,
Brian

_________________________________________________________________
The new MSN 8: advanced junk mail protection and 2 months FREE* 
http://join.msn.com/?page=features/junkmail


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org

RE: Modular packaging of a large application

[Daniel Perry <d....@netcase.co.uk>]

> 1) Should all my entity beans be packaged in a single jar?
>

no idea... i dont go in for the session beans/entity beans, i'm using OJB so
it's a bit different.

> 2) Different modules will probably mean different session beans, jsps and
> struts actions.
>

This is no problem.  Different modules all have their own config file, so as
long as the action classes/jsps dont overlap there wont be a problem.  I
would suggest you put the action classes for different modules in different
packages, and jsps in different folders.  That way, development can be as
independant as you like.

Daniel.


> -----Original Message-----
> From: Brian Styles [mailto:givemeadamnusername@hotmail.com]
> Sent: 19 May 2004 15:30
> To: struts-user@jakarta.apache.org
> Subject: Modular packaging of a large application
>
>
> Hi everyone,
>
> I've built an application in a standard j2EE format
>
> JSPs-->Struts-->Session Beans-->CMR Entity Beans.
>
> This is deployed in an exploded ear, with struts and JSPs in the
> war as well
> as the session bean interfaces. Then I have the Session Beans and
> CMR Entity
> Beans in a jar.
>
> Now I want to go to a larger environment where different developers are
> working on different modules, yet I still want each module to be
> accessable
> through a single point - ie, struts.
>
> Struts 1.1 has the concept of modules, allowing different struts config
> files per module, however, from the context of deployment I have some
> worries.
>
> 1) Should all my entity beans be packaged in a single jar?
>
> 2) Different modules will probably mean different session beans, jsps and
> struts actions.
>
> Therefore, I would really appreciate advice/experienc on packaging up an
> architecture like this.
>
> regards,
> Brian
>
> _________________________________________________________________
> The new MSN 8: advanced junk mail protection and 2 months FREE*
> http://join.msn.com/?page=features/junkmail
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
> For additional commands, e-mail: user-help@struts.apache.org
>
>


---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@struts.apache.org
For additional commands, e-mail: user-help@struts.apache.org