J2EE design help needed!

Hi all, I'm trying to develop an extensible architecuture to add new services to my existing website. I want this to be similar to www.salesforce.com, where each service is accessed via a main tab, and each service is essentially a mini-application in itself. I have an existing struts app which

RE: Modular packaging of a large application

e 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:[EMAIL PROTECTED] >

RE: Modular packaging of a large application

ky 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,

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

RE: [JBoss-user] [Beginners Corner] - deployment big picture

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