|
Search This Site: |
|
|||||||
| comp.lang.java.programmer Programming in the Java language. |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
#1 |
|
Join Date: Oct 2007
Age: 41
Total Posts: 2
|
J2EE Java Blueprints package/directory structure: best practice for common code?
I am working on several Java J2EE web applications using struts/
tomcat, and I have common Java code that I want to share between multiple J2EE web apps. Question: Is there a best practice for where common Java code should be placed in the J2EE Java BluePrints package/directory structure? http://java.sun.com/reference/blueprints/ Should this code be placed into a JAR file? Or, is it OK to include the common source files as part of the build for each app? Would it make any sense to place the code under apps? How about placing it in the root directory under src/java/com? I'm just looking for ideas. |
|
|
|
| Bookmarks |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Section | Replies | Last Post |
| [M68KNOMMU 00/06]: move common ColdFire code to its own directory | Greg Ungerer | linux.kernel | 0 | 1st February 2008 06:50 AM |
| Java/J2ee | willimm | comp.lang.c++ | 4 | 26th October 2007 09:24 PM |
| Java/J2ee | willimm | comp.lang.c++ | 0 | 26th October 2007 09:02 PM |
| Java/J2ee | willimm | comp.lang.c++ | 0 | 26th October 2007 09:02 PM |
| Java/J2ee | willimm | comp.lang.c++ | 0 | 26th October 2007 09:02 PM |