i'm trying to design a J2EE (1.4) project hierarchy for my JBoss 4.0 projects. i expect to be using most of the J2EE architecture components (EJBs, M-D Beans, servlets, JSPs) in the projects. on the tools side the projects will be using Ant (1.6), XDoclet (1.2) and possibly Hibernate (3.0). the project hierarchy should be durable and reusable in future J2EE projects. the projects are likely to be sharing code with each other.
i'm not really familiar with the different decisions and tradeoffs in choosing the hierarchy so i'd appreciate concrete hierarchy suggestions or discussions on the tradeoffs as well as pointers to discussions on this subject. below is the hierarchy that JBoss 3.0 Quick Start Guide (Draft 4) suggests for JBoss 3.0 projects. is this something that could be used as a basis? etc - bin # script file templates for running the code - meta-inf # non-generated deployment descriptors, manifest files main - client # client source - ejb # EJB source - servlet # servlet source resources # XDoclet resource files web # JSP pages build - bin # generated script files - classes # compiled class files - deploy # deoployable files - generate # XDoclet generated Java files - META-INF # XDoclet generated deployment descriptos - war # web archives br. aspa View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3866383#3866383 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3866383 ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click _______________________________________________ JBoss-user mailing list JBoss-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/jboss-user
