commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 32015] New: - Make CatalogBase.getCommand() thread safe
Date Tue, 02 Nov 2004 09:48:18 GMT
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: commons-dev@jakarta.apache.org
        ReportedBy: mail@manfred-wolff.de


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: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org


Mime
View raw message