Class cache usage causes make using different factory for different tables not
work.
------------------------------------------------------------------------------------
Key: DISPL-505
URL: http://jira.codehaus.org/browse/DISPL-505
Project: DisplayTag
Issue Type: Bug
Components: Configuration
Affects Versions: 1.1.1
Reporter: Mike Calmus
Attachments: TableProperties.patch
Because of the way TableProperites caches factory objects, it makes it
impossible to reliably specify different factories (factory.requestHelper,
factory.decorator, ...) for different table instances. The object cache is
keyed by the property name rather than the class name. As such, once one table
is used, the property value used by that table is the one that is used for all
subsequent tables. The attached patch does the object cache via the class name.
This allows multiple tables to work but still gives the caching benefit.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
-------------------------------------------------------------------------
SF.Net email is sponsored by:
Check out the new SourceForge.net Marketplace.
It's the best place to buy or sell services
for just about anything Open Source.
http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace
_______________________________________________
displaytag-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/displaytag-devel
