I'd love to see some examples of source code organization and packaging as it relates specifically to EJBs and Jboss. Things I'm looking for are:
1) Easy versioning - allow one EJB to evolve without impacting others. 2) Clean separation between client and server side classes, while dealing with common overlap between the two. 3) Easy packaging using ant. 4) Packaging which lets us get the most benefit of hot deployment. Especially curious how best to deal with the classes that may be exposed via the client. 5) Organizing a Castor-based bean's resources. I'd know there are as many ways of attacking this as there are J2EE technologies - so what have you found to work well? Or what doesn't work? Looking forward to your thoughts... Thanks! David ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Welcome to geek heaven. http://thinkgeek.com/sf _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-user
