"Geir Magnusson Jr." wrote:
> Yes. Let me ask a question.... What is the *real* problem? I suspect
> it will be how to solve the problem of partitioning template sets apart
> from one another for 'subapps' to avoid collisions....?
Template name collisions can be avoided by putting them into different
directories under the search path. That is easy to implement and would
work well for many applications. However there are more things in
Velocity
that have global scope than just template names (used as keys in the
cache):
- Configuration settings that affect rendering (each subapp might wish
to
configure Vel bit differently)
- VelociMacro libraries
- Introspection cache (each subapp uses a separate classloader, thus
they
can use classes with same names but incompatible interfaces)
The main idea behind subapps is that they will be developed separately
and
then assembled into a web application. Using separate Velocity engines
by each of them would help to decouple the sub-applictions, and decrease
neccessary communication between teams developing them.
Rafal
PS. Could you run the speed testing suite on the patched Vel, or tell me
real quick how to do it?
--
Rafal Krzewski
Senior Internet Developer
mailto:[EMAIL PROTECTED]
+48 22 8534830 http://e-point.pl
