[
http://jira.magnolia.info/browse/MAGNOLIA-2032?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Philipp Bracher updated MAGNOLIA-2032:
--------------------------------------
Description:
In 3.0 we used the commons discovery which takes care about synchronization.
For being on the save side we have to synchronize this method.
First I tried to solve it with a so called double-checked locking. Thanks you
Jan he advised me to read http://www.ibm.com/developerworks/library/j-dcl.html
was:
In 3.0 we used the commons discovery which takes care about synchronization.
For being on the save side we have to synchronize this method.
First I tired to solve it with a so called double-checked locking. Thanks you
Jan he advised me to read http://www.ibm.com/developerworks/library/j-dcl.html
> FactoryUtil.getSingleton should be synchronized
> -----------------------------------------------
>
> Key: MAGNOLIA-2032
> URL: http://jira.magnolia.info/browse/MAGNOLIA-2032
> Project: Magnolia
> Issue Type: Bug
> Components: core
> Affects Versions: 3.5.3
> Reporter: Philipp Bracher
> Assignee: Philipp Bracher
> Fix For: 3.5.4
>
>
> In 3.0 we used the commons discovery which takes care about synchronization.
> For being on the save side we have to synchronize this method.
> First I tried to solve it with a so called double-checked locking. Thanks you
> Jan he advised me to read http://www.ibm.com/developerworks/library/j-dcl.html
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.magnolia.info/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
