Application Structure

We are trying to design the best structure for our first application and need some guidance.

Any web sites with details on determing the best structure or just some advice

would be greatly appreciated.

Our application has several main areas which contain html, jsp, javascript, java classes, session beans and entity beans. The main areas within the app are:

- importcontains classes for importing various files.

- maintenance contains classes for matching data from the files to existing table data

- admincontains classes for maintaining tables

- commoncontains classes used by import, maintenance, admin.

How should the deployment be set up? Should each area be a separate EAR/WAR file?

We've been using JAR files to deploy to the app server and copying the jsp files through

Explorer but wanted to change to EAR/War files.

Currently, we are each working on our own sections.. I'm working on the import and have

some classes that should be moved to a common package so the developers working on maintenance and admin can also use them.

We are using JBuilder 5 and have our source code on our c: drive until we determine how we should structure the application. We haven't selected a Version Manager yet but may be using Rational at a later date. We use Jaguar 3.6.1 for our web/app server.

Thanks for any help!

RM

[1417 byte] By [rboarmana] at [2007-9-27 7:58:11]
# 1
Once you've got a release version, using a WAR file is the best way to do it.
tjacobs01a at 2007-7-8 12:32:06 > top of Java-index,Archived Forums,Java Programming...
# 2
first off I would do a google search for "model 2".Then peruse some of the links you find. Here is one of them http://www.javaworld.com/javaworld/jw-12-1999/jw-12-ssj-jspmvc.htmlThey might give you a good start on an app architecture.
pmonta at 2007-7-8 12:32:06 > top of Java-index,Archived Forums,Java Programming...
# 3

You should certainly use EAR/WAR to package your application(for versioning and deployment). That said, this will dictate some of your "structure". As far as separating the various components of your application in individual EAR/WAR packages, it seems non-standard. An EAR or WAR should represent a complete Enterprise or Web Application respectively. So, unless you're individual components could stand alone as separate applications, then I would argue that there should be only a single EAR/WAR.

I would also have a serious look at Struts(http://jakarta.apache.org/struts). It is a framework for developing applications following the Model 2 architecture. You could try to implement this yourself, but a lot of work has gone into Struts, it's stable, it's free, and it's open source. How can you go wrong?

Hope this helps,

- Phil

pzampinoa at 2007-7-8 12:32:06 > top of Java-index,Archived Forums,Java Programming...