See my previous email to Marcello on this topic. Marcello was correct in his
example, except there's another step involved to do this from a servlet or JSP.
The nice thing about the JRun-specific way of doing these things is that they
can be faster and more efficient internally. Using the ResourceManager is
non-standard, but it saves RMI overhead and object creation. It's a feature,
but as you point out, it has the limitation of being non-portable. Just as long
you realize that JRun also does things according to spec! :->
Scott Stirling
West Newton, MA
> -----Original Message-----
> From: Rhodes, Phillip C. [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, September 20, 2000 10:26 AM
> To: '[EMAIL PROTECTED]'
> Subject: [JRun-Talk] Non-Jrun specific way to get local EJBHomeObject?
>
>
> In JRun examples, they have the following code snippet that will get the
> local EJBHome object for this bean.
> final User user =
> ((UserHome)ResourceManager.getLocalEJBHome("sample10a.UserHome")).findByPrim
> aryKey(name);
>
> Although I love JRun :) I would like my code to not depend upon the
> container. If I have already have an existing javax.ejb.SessionContext
> object, how may I use this to objtain a reference to a local ejb home
> object?
>
> Thanks.
>
>
> Phillip Rhodes
> [EMAIL PROTECTED]
> Alcoa eCommerce
> https://www.ALCOADIRECT.COM
> 826B Two Allegheny Center Pittsburgh, PA 15212
> (412) 553-4900 (phone) (412) 553-2484 (fax)
------------------------------------------------------------------------------
Archives: http://www.egroups.com/group/jrun-interest/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists&body=lists/jrun_talk
or send a message to [EMAIL PROTECTED] with 'unsubscribe' in the
body.
