[
https://issues.apache.org/jira/browse/LABS-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12630882#action_12630882
]
Ryan McKinley commented on LABS-144:
------------------------------------
If the Map is ever manipulated after starup, it will need to be synchronized.
For many (most?) of the normal Factory implementaions, this is not an issue --
all the Protocol / parser / etc, are typically known at startup. However if we
want to dynamically add protocols, parsers, etc at runtime, it needs to be a
synchronized map.
Rather then synchronizing getMap(), we should make sure the map implementation
is thread safe (when necessary). ConcurrentHashMap or
Collections.synchronizedMap is a better option the synchronizing the parent
function.
All this is independent of the non-thread safe issues introduced by adding a
lazy loading initalizer.
> Consider making dependency on Spring / Cocoon Configurator optional
> -------------------------------------------------------------------
>
> Key: LABS-144
> URL: https://issues.apache.org/jira/browse/LABS-144
> Project: Labs
> Issue Type: Improvement
> Components: Droids
> Reporter: Oleg Kalnichevski
> Priority: Minor
> Attachments: droids.patch
>
>
> Please consider making dependency on Spring / Cocoon Configurator optional.
> Being a happy Spring user myself, I, nonetheless, think Droids API / Core
> classes should not depend on a particular DI framework / configuration
> format. It should be possible to split Droids code into API/Core module and
> runtime with only the latter being dependent on Spring / Cocoon Configurator.
> Oleg
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
