Hi Michael, First is from the J2EE-Patterns list...might solve some of your problems...
The Java BluePrints team (http://java.sun.com/blueprints) has posted an early access draft of coding and naming conventions for J2EE applications. This document is available at http://java.sun.com/blueprints/code/namingconventions.html This is the "best practices" you could follow...although it is a work in progress and I've found most don't follow it exactly...... Another good resource would be EJB Design Patterns from http://www.theserverside.com by Floyd Maru...(something) What we've finalised on here is the following: Directory of C:\aurium\caf\src\components\context 1/10/2002 15:38 <DIR> . 1/10/2002 15:38 <DIR> .. 3/10/2002 10:48 23,454 build.xml - build file 1/10/2002 16:22 278 component.properties - property file for this component 0/08/2002 13:11 <DIR> config - deployment descriptors see below 3/10/2002 12:45 <DIR> CVS - CVS stuff 3/10/2002 13:02 <DIR> deploylib - deploy classpath 1/10/2002 15:17 <DIR> net - listed below 8/10/2002 11:50 <DIR> resources - compile classpath 8 File(s) 49,457 bytes net.aurium.component. -> ejb (your abstract classes) -> impl (xdoclet generated classes) -> interfaces/client (your own classes (e.g business interfaces, and xdoclet generated ones) -> test (your own) -> util (your own utility classes) Directory of C:\aurium\caf\src\components\context\config 0/08/2002 13:11 <DIR> . 0/08/2002 13:11 <DIR> .. 5/10/2002 14:58 <DIR> CVS 0/08/2002 13:11 <DIR> ear 0/08/2002 13:11 <DIR> ejb-jar 0/08/2002 13:07 <DIR> test-ear 1/09/2002 09:48 <DIR> test-war 0/08/2002 13:11 <DIR> war Then in each folder we haves ome thing like: Directory of C:\aurium\caf\src\components\context\config\ejb-jar 20/08/2002 13:11 <DIR> . 20/08/2002 13:11 <DIR> .. 30/08/2002 10:13 <DIR> META-INF 0 File(s) 0 bytes Directory of C:\aurium\caf\src\components\context\config\ejb-jar\META-INF 30/08/2002 10:13 <DIR> . 30/08/2002 10:13 <DIR> .. 31/10/2002 13:33 34,960 ejb-jar.xml 31/10/2002 13:33 7,908 jaws.xml 31/10/2002 13:33 1,647 jboss.xml 31/10/2002 13:33 17,262 jbosscmp-jdbc.xml 4 File(s) 61,777 bytes Hope this helps, But this is of course just my 2c... Oisin -----Original Message----- From: [EMAIL PROTECTED] [mailto:xdoclet-user-admin@;lists.sourceforge.net] On Behalf Of Michael Hedgpeth Sent: 31 October 2002 15:37 To: [EMAIL PROTECTED] Subject: [Xdoclet-user] Package/Directory Management Best Practices I am trying to migrate from JBuilder to IDEA and XDoclet. With JBuilder, we put all of our EJB classes in one package and the ejb descriptors handled the build process behind the scenes, building roughly 25 different ejb jar files from that one package. It doesn't look like this will work with XDoclet. So, I'm wondering, what is the recommended best practice for package management? Do you have an enterprise bean per package? If so, what do you do with the deployment descriptors? Do you generate everything at build time? Then how do you account for errors throughout the IDE saying it can't find your Remote Interface classes? Thanks, Michael Hedgpeth Software Development Consultant Fair, Isaac & Co., Inc. formerly HNC ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user ------------------------------------------------------- This sf.net email is sponsored by: Influence the future of Java(TM) technology. Join the Java Community Process(SM) (JCP(SM)) program now. http://ads.sourceforge.net/cgi-bin/redirect.pl?sunm0004en _______________________________________________ Xdoclet-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/xdoclet-user
