Hi,
> The major problem of putting entities separated from
> the session beans is that entities typically are more
> object-oriented and communicate using fine-grained
> method-calls, while sessions are service-oriented
> using coarse-grained method-calls. The services
> fullfill their coarse-grained operations using several
> fine-grained method calls on the entities.
> This makes it necessary (for performance/scaleability)
> to put the entities and sessions in the same
> address-space (ie. using local calls).
>
> So the irony here is: For performance the entity
> should be close to the data and the session should be
> close to the entity.
Extremely good point.
--
Uddipan Bagchi
Associate Consultant,
e-Commerce Division,
e-Enabling Solutions,
WIPRO Ltd.,
3rd Floor, Basappa Complex,
40/1A, Lavelle Road,
Bangalore - 1.
Phone:(080)-2215010 - Ext. 314
(080)-6680876 (PP)
mailto:[EMAIL PROTECTED]
http://www.wipro.com
The World's First SEI CMM Level 5 Software Services Company
===========================================================================
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".
