DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=32015>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=32015 Make CatalogBase.getCommand() thread safe Summary: Make CatalogBase.getCommand() thread safe Product: Commons Version: 1.0 Alpha Platform: All OS/Version: Other Status: NEW Severity: Normal Priority: Other Component: chain AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] I use commons-chain to implement filters and strategies. If several instances shared the same catalog there are problems with the getCommand() implementation, because the method itself is not thread safe and the implementation of the map also. So there are several possibilities: 1. Add a comment to the java doc, that this implementation is not thread safe. 2. Use Hashtables instead of HashMap for the commands. 3. Offer a synchronized decorator for the CatalogBase class. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
