It would be really nice if the EJB architecture handled the creation of
coarse-grained communication.  That is, the beans are designed with
fine-grained property accessors, but the Application Assembler can declare
which properties are batched & cached by the remote proxy.

This could get tricky with the setter-methods, but very useful.

-----Original Message-----
From:   A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]] On Behalf Of Ian McCallion
Sent:   Wednesday, June 16, 1999 9:34 AM
To:     [EMAIL PROTECTED]
Subject:        Re: Using collection bean to represent a list of entity
beans-             was RE : Application Server container related question

Sachin Aggarwal wrote:
1. Agressive local optimisation of inter-bean calls
   that violates the EJB spec (as done by Weblogic)
2. Smart Proxies (as per Rickard Oberg's package)
3. Anticipatory loading of entity beans (not sure
   who claimed to do this - I think it was Gemstone)
4. My hack above

are all attacking different aspects of the same problem, namely the
granularity of object models vs the granularity of architected server-side
objects. The ideal solution, in my opinion, would be to allow every object
in the model to be an efficiently callable CMP "sub-entity bean" and to
compose sub-entities at deployment time into coarse-grained entity beans
working approximately as I described above. Unfortunately "sub-entity
beans" are not yet architected.

</soapbox)



Ian McCallion
CICS Business Unit
IBM Hursley
[EMAIL PROTECTED]
Tel: ++44-1962-818065
Fax: ++44-1962-818069

===========================================================================
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".

===========================================================================
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".

Reply via email to