Hi Ashwani, Ideally you should divide your system in to various subsystems. Each subsystem should have clear defined interface. The subsystem can contain one or more classes. The subsystem can be divided on the basis of work, the deployments to get performance gain and also the the domain. The interfaces that the subsystem exposes should be the ones which are LESS likely to change and which are agreed as a contract between the other subsystems. i.e. The other subsystems can have those assumptions regarding the subsytem implementing those interfaces. Inside the subsystem you have the things which MOST likely will change. If the interfaces between the subsystems are agreed upon by the Architect(s) and the subsystem leads. Each subsystem can continue working on implementing their respective implemenation behind their subsystem interface. So that when they one to intereate, they can seamlessly do that. Each subsystem can have their own stubs for other subsytems, so that during integration the subsystems can be replaced by the real implemenation.
thanks & regards, Siddhartha Software Architect http://www.visioncodified.com Quoting Ashwani Kalra <[EMAIL PROTECTED]>: > Hi, > > I want to get your openion on how to divide the work of session bean with > developers. Each one is using WSAD 4.0. If we divide the session beans > according to module, then each one is writing different functionalities > with in that session bean. How to integrate each one work into one session > bean ? > > TIA > Ashwani Kalra > > > > > > ------------------------------------------------- This mail sent through IMP: http://horde.org/imp/ =========================================================================== To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff EJB-INTEREST". For general help, send email to [EMAIL PROTECTED] and include in the body of the message "help".
