Henning-
On May 9, 2004, at 4:37 PM, Henning P. Schmiedehausen wrote:
You might either want to have some sort of real life cycle (which would be overkill for a point release like 2.3.1) or, if just Class.forName() is your bottleneck, simply store the Class objects and not the instance objects. This could even be a class cache, not just an instance cache, because translating "com.mycorp.modules.actions.FooAction" to a Class object describing the FooAction class is the same for all the instances.
Great point. I have re-implemented this as a Class cache, since Class.forName() is indeed our bottleneck, and I will be testing it over the next few days. I will send my patched patch when satisfied that it is doing the right thing...
-B
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
