camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Willem Jiang (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-4137) CxfNamespaceHandler should not just set the TCCL and not set it back
Date Mon, 27 Jun 2011 09:32:47 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-4137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13055423#comment-13055423
] 

Willem Jiang commented on CAMEL-4137:
-------------------------------------

This issue need to a new release of CXF, Current solution just a workaround, it has some side
effects.
I think we can post it to Camel 2.9.0, as we are closing to the Apache Camel 2.8.0 release.

> CxfNamespaceHandler should not just set the TCCL and not set it back
> --------------------------------------------------------------------
>
>                 Key: CAMEL-4137
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4137
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-cxf
>            Reporter: Willem Jiang
>            Assignee: Willem Jiang
>             Fix For: 2.8.0
>
>
> Current CxfNamespaceHandler set the TCCL to parser the cxfEndpoint, but it never reset
the TCCL back.
> It will cause some trouble if there are lots of Blueprint Namespcehandlers are called
by the same thread.

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

        

Mime
View raw message