> -----Original Message-----
> From: Ryan Hoegg [mailto:[EMAIL PROTECTED]]
> Sent: Monday, July 15, 2002 7:34 PM
> To: [EMAIL PROTECTED]
> Subject: Re: JNDI Dependency
>
>
> Hi,
>
> I just compiled 2.0.3 and it still gave me the same error about JNDI as
> before.  Something is not seeing the presence of JNDI in JDK 1.4.
>
Yes, this is still a problem - we didn't fix it for 2.0.3. Sorry.

Carsten

> Ryan Hoegg
> ISIS Networks
>
> Original thread:
>
> Vadim Gritsenko wrote:
> >
> > > From: Ryan Hoegg [mailto:[EMAIL PROTECTED]]
> > >
> > > You know, something else that bugs me is this error message:
> > >
> > > op-warning:
> > > **********************************************
> > > *
> > > *  Classes of the optional package JNDI are not
> > > *  available. Apache Cocoon builds without them.
> > > *
> > > *  JNDI is required for the ldap generator and the parentcm generator.
> > > *
> > > *  Recovery:
> > > *  Get the jndi.jar from Sun and place the jar in the lib/optional dir
> > > *
> > > ***********************************************
> > >
> > > JNDI is integrated into the JDK 1.4; it's no longer available as a
> > > separate package.  Shouldn't the build recognize that?
> >
> > Carsten,
> >
> > Should <path id="classpath"> have reference to the rt.jar? Are there any
> > issues with that?
> >
> Hmmm, as our build system already distinguished between 1.2/1.3
> and 1.4 this
> should work, I think.
>
> Carsten
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, email: [EMAIL PROTECTED]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to