Welcome to the new Spring.io forums!
If this is your first visit, be sure to check out the
by clicking the link above, and for security reasons, use the
forgot password link to reset your password..
You may have to register before you can post: click the register
link above to proceed. To start viewing messages, select the forum that you want to visit
from the selection below.
No announcement yet.
App. with EJBs - package and class structurePage Title Module
I was just reading R. Johnson's book 'J2EE D&D' and looking at Ticket app.
He somehow groups similar bussines and domain model objects. He separates type (EJB or no) by parent package (both client/server) from which two - ejb and support are made. But he then 'manualy' copies client dependant ejb classes. Ok, this is a small app., with just one ejb class, so it is easy to maintain. What about big stuff?
Ok, this is usage (bussines) oriented. What about container dependent - having server, client, common packages? Or is previous approach better and this one hard to implement?
Ok, I made some small EJB projects, where I really didn't care how the structure looked. But before moving to some bigger server/web client project, I would just like to know what the appropriate practice is. Just to be able to deploy as easy as possible (not just me, but anybody who contributes to the project - so that is point straight what to include in different container archive).