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

Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2012/09/14 13:43:08 UTC

[jira] [Commented] (CAMEL-5611) Issue with JndiContext in camel tests

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

Claus Ibsen commented on CAMEL-5611:
------------------------------------

This is not yet an ideal patch, as static variables is *bad*. When you have multiple camel contexts in the JVM etc.

I think we can offer 2 kind of ctx factory. Then you can chose the ones you want. One with the static reference, which is more suited for unit testing.
                
> Issue with JndiContext in camel tests
> -------------------------------------
>
>                 Key: CAMEL-5611
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5611
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-test
>    Affects Versions: 2.10.1
>            Reporter: Benjamin Graf
>            Priority: Minor
>         Attachments: CAMEL-5611.patch, cameljnditest.zip
>
>
> If you configure the jndiregistry in a unit test produced by CamelInitialContextFactory via jndi.properties you'll always get a new empty JndiContext if any library or component in between does a new InitialContext() call.

--
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