Hey Ricardo,

absolutely. But I said in "a" standard format. Not "the" standard format :-)


From: "Ricardo Cortes" <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: RE: Modular packaging of a large application
Date: Wed, 19 May 2004 11:15:56 -0400

Not to be cheeky but who says JSP->Struts->Session Beans->Entity Beans is the standard J2EE format?

:P

What about JSP -> Tiles -> Struts -> Business Delegate -> DAO -> Hibernate on JBoss?

-----Original Message-----
From: Brian Styles [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 19, 2004 10:30 AM
To: [EMAIL PROTECTED]
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: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]




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



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to