Hello Craig,
Wednesday, June 20, 2001, 8:52:18 PM, you wrote:
CRM> On Wed, 20 Jun 2001, Oleg V Alexeev wrote:
>> Hello Craig,
>>
>> Interesting question and clear answer... 8)
>>
CRM> Yah, I really enjoy the interesting ones :-).
>> What do you think about such caching for Class? With this approach we
>> call forName() method only once - no other overhead.
>>
CRM> Class loaders do this kind of caching already, so I guess I don't see all
CRM> that much benefit.
CRM> For Struts in particular, if you're concerned about repeated
CRM> Class.forName() calls, a better strategy is avoidance -- arrange your
CRM> application so that the form beans are created for you ahead of
CRM> time. Then Struts will never have to call it.
Sorry, but I have not idea how to do so. Explain please, how can I
"arrange your application so that the form beans are created for you ahead of
time"? Is it step in struts-config or no?
CRM> Or, throw you can just throw hardware at it and take advantage of Moore's
CRM> Law ... :-)
--
Best regards,
Oleg mailto:[EMAIL PROTECTED]