Hi!
As EJB container promises transation, security, persistance for the bussiness
objects. Hence we are not coding a single line in our bussiness objects to meet
these requirements. During the deplpyment time of the EJB been we specify these
setting in the Deployment descriptor.
On seeing these DD specification, the container generates a wrapper class to
your bussiness object which contains the code to sustain transaction, securtiy
and persistance and creates an instance of this object and binds it to JNDI.
Hence client (servlet) can't directly say new ClassName().. consturctor as the
real class is not the one you have coded but the one EJB container has generated
during EJB Deployment
Nagendra
Placed At :
Naveen Chandra <[EMAIL PROTECTED]> on 12/08/2000 02:48:05 PM
To: Nagendra R/Satyam@Satyam
cc: [EMAIL PROTECTED]
Subject: EJB doubt
Hi Nagendra,
Thanks lot for your explanation on the lookup, Do you
mind sharing again for this doubt.
Why does client access an Enterprise JavaBean
by looking up the class implementing its home interface
by name through JNDI and then uses the methods
of home interface to acquire access to
an instance of the class implementing the remote interface ?
Why cannot client access the remote interface directly ?
By doing this client --> EJBHome --> EJBObject
in the EJB architecture what advantage they get ?
It seems I am fully confused now with the EJB implementaion ?
And why did they kept all business methods in the Remote interface and
create and finders in home interface. I think I may be asking
very silly questions, but it really makes me too confusing to
understand the EJB architecture and its implementaion.
Do you mind sharing your knowledge with me in this regard.
Thanks,
Naveen.
===========================================================================
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".
