tapestry-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Howard M. Lewis Ship (JIRA)" <j...@apache.org>
Subject [jira] Closed: (TAP5-84) Change proxy generation to use volatile fields rather than synchronized blocks
Date Wed, 04 Mar 2009 17:35:57 GMT

     [ https://issues.apache.org/jira/browse/TAP5-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Howard M. Lewis Ship closed TAP5-84.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 5.1.0.1

> Change proxy generation to use volatile fields rather than synchronized blocks
> ------------------------------------------------------------------------------
>
>                 Key: TAP5-84
>                 URL: https://issues.apache.org/jira/browse/TAP5-84
>             Project: Tapestry 5
>          Issue Type: Improvement
>    Affects Versions: 5.0.15
>            Reporter: Howard M. Lewis Ship
>            Assignee: Howard M. Lewis Ship
>            Priority: Minor
>             Fix For: 5.1.0.1
>
>
> As currently coded, the service proxies used for Tapestry services use a synchronized
block to a) check to see if the Registry has shut down and b) obtain (if needed) the realized
service implementation (wrapped by interceptors, etc.).
> It seems that with some juggling, these could largely be replaced with AtomicBoolean
and AtomicReferences.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message