camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Sramka (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CAMEL-5835) XPathBuilder is documented as being thread-safe, but it has thread-safety bugs.
Date Thu, 29 Nov 2012 22:34:58 GMT

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

Peter Sramka updated CAMEL-5835:
--------------------------------

    Comment: was deleted

(was: For example, shown here are all uses of the instance variable bodyFunction. Access to
this variable is "incorrectly synchronized," as defined by http://www.cs.umd.edu/~pugh/java/memoryModel/jsr-133-faq.html)
    
> XPathBuilder is documented as being thread-safe, but it has thread-safety bugs.
> -------------------------------------------------------------------------------
>
>                 Key: CAMEL-5835
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5835
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-core
>         Environment: This bug is not environment specific.
>            Reporter: Peter Sramka
>              Labels: thread-safety
>         Attachments: screenshot-1.jpg
>
>   Original Estimate: 8h
>  Remaining Estimate: 8h
>
> The javadoc for org.apache.camel.builder.xml.XPathBuilder states that it is thread-safe,
but an inspection of the source code in the trunk reveals that there are thread-safety bugs.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message