Hi Jim ,
See below:
Jim Archer wrote:
> Hi All...
>
> I spent some time fighting something involving name service and I
> seriousely don't know if its a bug or a feature.
>
> I created a stateless session bean to provide a serice. I then wrote a
> class to wrap that SLSB with a has-a relationship. When the wrapper class
> is instansiated the code that instansiated it sets some properties and then
> calls its execute method. The execute method would lookup the SLSB useing
> the java:comp/env namespace and make it do its thing.
>
If I understand you correctly your wrapper class is a regular class - not an
ejb so therefore it can not access java:comp/ejb namespace. Each bean has it
own java:comp/ejb namespace where it can bind references and env-entrys and
this namespace is only availbale from the actual ejbean code.
Regular class acting as a client has an access to global JNDI namespace not to
java:comp/ejb namespace.
Latest JNDIView MBean shows nicely everything that is available in JNDI
namespaces but again not *everything* is available to your client. It all
depends in which thread your client is runnning i.e ClassLoader your client is
associated with.
Vladimir
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
