> > The need to have a SLSB before a SFSB is that SLSB acts like a worker so > > that it does all the working logic on the result got from the SFSB > performs > > some operations on it and sends them across to the client which simply > > presents them. > > In most other cases the client needs to do some operations on the result > got > > from the EJB's. > > Refer to some nice books on EBCA architechture (enterprise business > > component architechture).
Could you explain to me what operations these are, and why they are not simply done in the sfsb? I would see this breakdown of responsibilities: SFSB - queries/updates entity beans/database, and returns appropriate data web tier - presents data appropriately. I dont see what needs to be done between the sfsb and the web tier. cheers dim ps - I'm always interested in peoples recommendations for books - what books do you consider to be "nice books on EBCA arch"? tia =========================================================================== 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".
