JNDI support for EJBs

[Berin Loritsch <bl...@apache.org>]

Has anyone considered the fix I had for EJB environments?
I would like to commit what I have if possible.  Basically,
if ServiceClient can detect an installed JNDI implementation,
it will attempt to use it.  If not, it creates a new AxisClient
directly.  That way we are not dependant on other jars, and
it works as expected.

Re: JNDI support for EJBs

[Berin Loritsch <bl...@apache.org>]

Glen Daniels wrote:
> 
> I asked people to vote on it last week, and heard nothing except my +1.
> 
> I'd say commit it, but I might make one additional caveat, which is to modify
> the code to use reflection to call the JNDI interfaces.  This would mean people
> could build Axis without a JNDI jar kicking around.  Alternately, can we
> distribute jndi.jar in the axis lib/ directory?

If we are targeting JDK 1.3+ then there is nothing more that needs
to be done.

I might lean toward a JNDI jar in the repository because reflection
for strictly compilation purposes is a bit much.  Reflection is a
great tool for factory code and things like that though.

> 
> --Glen
> 
> ----- Original Message -----
> From: "Berin Loritsch" <bl...@apache.org>
> To: "Axis Development" <ax...@xml.apache.org>
> Sent: Monday, October 08, 2001 1:11 PM
> Subject: JNDI support for EJBs
> 
> > Has anyone considered the fix I had for EJB environments?
> > I would like to commit what I have if possible.  Basically,
> > if ServiceClient can detect an installed JNDI implementation,
> > it will attempt to use it.  If not, it creates a new AxisClient
> > directly.  That way we are not dependant on other jars, and
> > it works as expected.
> >
----------------------------------------------------
Sign Up for NetZero Platinum Today
Only $9.95 per month!
http://my.netzero.net/s/signup?r=platinum&refcd=PT97

Re: JNDI support for EJBs

[Glen Daniels <gd...@macromedia.com>]

I asked people to vote on it last week, and heard nothing except my +1.

I'd say commit it, but I might make one additional caveat, which is to modify
the code to use reflection to call the JNDI interfaces.  This would mean people
could build Axis without a JNDI jar kicking around.  Alternately, can we
distribute jndi.jar in the axis lib/ directory?

--Glen

----- Original Message -----
From: "Berin Loritsch" <bl...@apache.org>
To: "Axis Development" <ax...@xml.apache.org>
Sent: Monday, October 08, 2001 1:11 PM
Subject: JNDI support for EJBs


> Has anyone considered the fix I had for EJB environments?
> I would like to commit what I have if possible.  Basically,
> if ServiceClient can detect an installed JNDI implementation,
> it will attempt to use it.  If not, it creates a new AxisClient
> directly.  That way we are not dependant on other jars, and
> it works as expected.
>