Hi,
Whenever you invoke remote methods, the call will be streamed and sent to
the destination machine. The container out there will have to marshall it to
know which method to invoke. Firstly this increases the network traffic and
the overhead of marshalling decreases the response time.
Consider an example. You have to call 2-3 entity beans in sequence and the
result of next call to entity depends on the previous one. Then from your
client(say jsp) instead of calling these three beans separately you call fn
of session bean which in turns call these entity beans. Thus there will be
network traffic of one call instead of three calls.
Also you can change the implementation of the fn of the session bean without
changing your client.
========================
Regds
Ashwani Kalra
Aithent Technologies
India
========================
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Hemant Arora
Sent: Tuesday, July 17, 2001 11:44 AM
To: [EMAIL PROTECTED]
Subject: Wrapping the entity bean wiht session bean
Hi
Please could some one provide some substantial reasons for wrapping the
entitty beans with the session beans.
As in in the discussion forums it is said that the network calls are
reduced
Please someone could provide some examples
Thanks
Hemant
===========================================================================
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".
