> Could that feature ever make a $LicenseToKill() tool available in places > that you wouldn't want it?
If you have only one VVS it is already the case. If you have several VVS, then they can use different toolbox.xml, or the same, as before. The point here is just to avoid re-initializing application/session scope tools for each servlet (and that is a little more complex than I thought, since one has to avoid collisions between tools if servlets use different toolbox.xml files, or also collisions between different webapps in runtimeSingleton mode... but nothing too hard I guess). CloD ----- Original Message ----- From: "Tim Colson" <[EMAIL PROTECTED]> To: "'Velocity Developers List'" <[EMAIL PROTECTED]> Sent: jeudi 9 janvier 2003 18:20 Subject: RE: [VELTOOLS] Why isn't ServletToolboxManager a singleton class ? > > Yes, that would be nice. Does anyone see drawbacks > > to sharing tools between VV Servlet? I don't. > Could that feature ever make a $LicenseToKill() tool available in places > that you wouldn't want it? > > Tim > > > -- > To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
