[webbeans-issues] [JBoss JIRA] Commented: (WBRI-195) application context isn't thread safe

Takeshi Kondo (JIRA) jira-events at lists.jboss.org
Mon Mar 23 11:06:25 EDT 2009


    [ https://jira.jboss.org/jira/browse/WBRI-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12458572#action_12458572 ] 

Takeshi Kondo commented on WBRI-195:
------------------------------------

> We are planning a centralized Seam-like @Synchronized solution after interceptors are done 

I don't think that it will resolve this issuse.
Does Seam-like @Synchronized solution mean method call time synchronization?
This issue is construct time synchronization, so @ApplicationScoped doesn't guarantee Singleton.
google-guice has same logic in @Singleton object initialization.

> application context isn't thread safe
> -------------------------------------
>
>                 Key: WBRI-195
>                 URL: https://jira.jboss.org/jira/browse/WBRI-195
>             Project: Web Beans
>          Issue Type: Bug
>          Components: Contexts
>    Affects Versions: 1.0.0.BETA1
>            Reporter: Takeshi Kondo
>            Assignee: Nicklas Karlsson
>             Fix For: 1.0.0.CR1
>
>         Attachments: test_code.patch, thread_safe_application_context.patch
>
>
> Application scoped object initialization isn't synchronized.
> so if initialization in concurrent request , create more than one instance.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the weld-issues mailing list