Krish,
Firstly, Avi had a good point.. the key to ejb-link is giving you the
deployment time flexibility to decide which home to use - which may in-fact
be the Same class deployed with different run-time qualities and under a
different name.
But, I'm a bit confused.. remember that the Home you get is always a
proxy... You don't get to talk to the back-end at all. So it's not like a
Java interface and is inherently pass-by-reference regardless of what VM
it's on.
Jon
************************
Jon Ferguson
ObjectTalk
email: [EMAIL PROTECTED]
************************
>In EJB 1.1, defining ejb-links between EJBs implied that you
>would do something along the lines of a
>"jndiContext.lookup("java:comp/env/ejb/SomeHomeName"
>and exactly the same is required for a lookup of
>a *local* home interface in EJB 2.0. But my question
>was why would you want to 'lookup a local home interface'
>(using ejb-links again)?
>
>Wouldn't something instead along the lines of
>"LocalHomeClass.getReference()" be a better idea?
>Another argument for something along the above lines
>would be that local and remote interfaces are not
>interchangeable and the fact that you cannot 'convert'
>one to the other. So in fact, they are fundamentally
>different, and behave differently as well (pass by
>reference et al).
>
_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com
===========================================================================
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".
