Domain Object and Service oriented pattern
We have J2EE based application with following components, we are facing some issues with existing system.
Current System : We have J2EE based application. The following is the flow.
Client Layer [including JSP, Struts ] action classes Delegates Session fa鏰de [Session bean] DAO EJBDAO EJB. We use CMP, xDoclets , JBOSS.
1.Our Domain objects are heavy. I know they are suppose to be coarse objects but they take more time in loading. Also, we noticed one thing that lot of methods are called during Domain Object creation process and it takes lot of time in loading. Actually, we dont really know what is happening as we are using CMPs.
Question :
-Any input on what can be done to avoid Domain object excessive loading time.
-Anyone can share there experiences with Domain objects. Are you facing issues related with performance.
-We dont use DTO, we pass domain objects between. Do you see any problem in doing that.
2.Currently, our system was used by one single front end or lets say we have only one client but soon we will have more clients using it.
Question :
-What should be our design approach. How can we make our system more like service oriented. If the two clients demand different business logic then how it will be handled. Business logic common to all the clients will be handled by which layer and business logic specific to client will be handles by which layer.
-Please suggest based on our existing infrastructure. We don抰 want to use SOAP or cannot make drastic changes to our flow.
We have domain and services in the same package and we are doing the refactoring of code, your inputs will be valuable.
Thanks
Sandipan
