You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@servicemix.apache.org by "Gert Vanthienen (JIRA)" <ji...@apache.org> on 2011/06/07 10:10:59 UTC

[jira] [Resolved] (SMXCOMP-880) Refactor servicemix-http component to avoid use of wrapper for locking

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

Gert Vanthienen resolved SMXCOMP-880.
-------------------------------------

    Resolution: Fixed

Fixed in http://svn.apache.org/viewvc?view=revision&revision=1132898

> Refactor servicemix-http component to avoid use of wrapper for locking
> ----------------------------------------------------------------------
>
>                 Key: SMXCOMP-880
>                 URL: https://issues.apache.org/jira/browse/SMXCOMP-880
>             Project: ServiceMix Components
>          Issue Type: Improvement
>          Components: servicemix-http
>    Affects Versions: 2011.01
>            Reporter: Gert Vanthienen
>            Assignee: Gert Vanthienen
>             Fix For: 2011.02
>
>
> Currently, the servicemix-http consumer endpoint uses the continuation itself or a wrapper around the continuation to synchronize on.  Since it can be a bit confusing for people (incl. myself) reading the code to figure out what exactly the synchronized block is using, it would be better to refactor this so it always uses a separate lock object.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira