Nevermind. I understand now. I'm use the singleton mode, not the
concurrent mode (Velocity is configured deeply underneath a couple other
packages, so this is the first time I've had to dust off the internals
of the engine). Fixing this will simply entail figuring out how the
other packages initializing.
Thanks for your help, set me on the track to figuring this out.
Ryan Clifton wrote:
Are there some disadvantages to the Singleton API? It would seem to
me that that should be the default unless there's a significant
problem with it.
Thanks for you answer, I found some docs about the Singleton API.
Digging into it now.
Nathan Bubna wrote:
Velocity will only do that if you use the singleton API. If you use
separate VelocityEngines for each app, then you shouldn't have a
problem.
On 1/12/07, Ryan Clifton <[EMAIL PROTECTED]> wrote:
Hello,
I am trying to run multiple web-apps under a single JVM that are
concurrently running their own velocity engines. When I start
everything up, the web-apps appear to use the template directory from
the first web-app that is loaded into the JVM.
IE. if i have www.foo1.com and www.foo2.com and foo1 is loaded first,
foo2 will only get templates from foo1.
So it seems that Velocity statically loads the templates folder across
the whole JVM. Is there any way around this other than running multple
JVMs on different ports?
thanks.
Ryan
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
