on 5/28/01 5:35 PM, "Dan Finkelstein" <[EMAIL PROTECTED]> wrote:
> Yes, both velocity engines are in the same JVM. I was thinking that if the
> api supported something like the following, then multiple engines could be
> supported at one time:
>
> Velocity velocity1 = Velocity.newInstance();
> velocity1.init();
> velocity1.mergeTemplate();
> ....
> Velocity velocity2 = Velocity.newInstance();
> velocity2.init();
> velocity2.mergeTemplate();
>
> To be more specific as to my unique needs, in our servlet-based application,
> like many people, we use Velocity for the normal html page processing. But,
> in addition, we might invoke it for some "preprocessing" of a very different
> nature. These two uses of the velocity templates can each occur at any time,
> so I'd really like to have two already initialized setups of velocity, each
> ready to run at any time.
>
> Dan
The solution is that you will most likely need to put one instance in one
classloader and another instance in another classloader.
Thanks,
-jon
