Jose Alberto Fernandez wrote:
>
> > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> >
> > Jose Alberto Fernandez wrote:
> > >
> > > > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED]]On
> > > >
> > > > What is EAS?
> > > >
> > > > I would figure you shouldn't be near a bootstrap classloader
> > > > in a webapp
> > > > environment.
> > > >
> > > > Were are you putting the velocity.jar? in the classpath?
> > > >
> > >
> > > But shouldn't this work correctly even if put in the
> > classpath? One may try
> > > to use velocity in projects that define its own server
> > architecture, not
> > > necessarily a web-app in a J2EE compliant WebServer implementation.
> > >
> > > No?
> >
> > Do you think we can try to get to the root of the problem first? This
> > is a rather unconventional problem - I use velocity all the
> > time outside
> > of a webapp environment (and so do you - you used to anyway), so lets
> > try and get a handle on what's going on?
> >
> > Yes?
> >
>
> Definetly, no problem with that.
>
> One reason may be the version of the JVM he is using. If I remember
> correctly, in the past the classpath was loaded using the "system"
> classloader which was represented as "null". But I think in 1.2 now we have
> the Bootstrap classloader (the "null" one) and the system classloader which
> is use to load the classpath and it is a regular classloader.
>
> Maybe he is using an older JVM architecture.
Yes - I should have asked the smarter question, which JVM. :)
Ok : which JVM?
geir
--
Geir Magnusson Jr. [EMAIL PROTECTED]
System and Software Consulting
Developing for the web? See http://jakarta.apache.org/velocity/
You have a genius for suggesting things I've come a cropper with!
