DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23359>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=23359

MessageResources Caching

[EMAIL PROTECTED] changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX



------- Additional Comments From [EMAIL PROTECTED]  2003-09-23 19:54 -------
John, the only way to stop the MessageResources class from caching the values it
receives is to dump the protected map of formatted messages with each call. 
Doing so will cause quite a performace hit on your application so I don't
recommend it.

The implementation that David mentioned does what I mentioned above, but the
underlying data access (OJB) has its own caching implementation, so you won't
notice a perf drop if you use that.  It also has the ability to turn off caching
(like say.....during development).

I am closing this because it isn't something anyone is going to change now or in
the future.  In fact, take a look at commons-resources (in the sandbox).  That
is what struts will (eventually) use soon.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to