hi tony
can u tell me where is the <transaction-isolation> comes into ejb-jar.xml

----- Original Message -----
From: Luong, Tony S322 <[EMAIL PROTECTED]>
To: Orion-Interest <[EMAIL PROTECTED]>
Sent: Tuesday, December 05, 2000 6:50 PM
Subject: RE: Traversing JNDI namespace


> java:comp/env entries are defined by the developer for each bean in
> ejb-jar.xml under the <env-entry> tag.
>
> > -----Original Message-----
> > From: Gary Shea [SMTP:[EMAIL PROTECTED]]
> > Sent: Monday, December 04, 2000 8:58 PM
> > To: Orion-Interest
> > Subject: Re: Traversing JNDI namespace
> >
> > On Today, Nick Newman ([EMAIL PROTECTED]) wrote:
> > > Hi,
> > >
> > > How can I find what's in an entity bean's java:comp/env namespace?
> > >
> > > If I ask the InitialContext for a list of what is in it (using
> > > initialcontext.list("") ) I get a list of things (mainly home
> > interfaces)
> > > plus entries for "java:comp" and "ejb" which are both Contexts.
> > >
> > > If I ask for what's in "java:comp" I get a few strange entries, but
NOT
> > one
> > > for "env", which is the one I would have expected.
> > >
> > > If I ask for what's in "java:comp/env" I get nothing back (empty
> > context).
> >
> > Just wanted to report that I've had exactly the same experience,
> > assumed I must be doing something wrong given my slight experience
> > with JNDI.
> >
> > I sure hope someone knows the answer!
> >
> > Gary
> >
> > >
> > > However, lookups for entries named java:comp/env/foo succeed where
they
> > should.
> > >
> > > Any ideas?
> > >
> > > Thanks,
> > > Nick
> > >
> > >
> > >
> >
> >
> >
>
> --------------------------------------------------------------------------
----
> CONFIDENTIALITY NOTICE: If you have received this e-mail in error, please
immediately notify the sender by e-mail at the address shown.  This e-mail
transmission may contain confidential information.  This information is
intended only for the use of the individual(s) or entity to whom it is
intended even if addressed incorrectly.  Please delete it from your files if
you are not the intended recipient.  Thank you for your compliance.
>
> ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>



Reply via email to