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

Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2008/10/19 13:59:53 UTC

[jira] Created: (CAMEL-998) Component should check for camel context is not null

Component should check for camel context is not null
----------------------------------------------------

                 Key: CAMEL-998
                 URL: https://issues.apache.org/activemq/browse/CAMEL-998
             Project: Apache Camel
          Issue Type: Improvement
          Components: camel-core
    Affects Versions: 1.4.0
            Reporter: Claus Ibsen
            Assignee: Claus Ibsen
             Fix For: 1.5.0


When creating components manually etc. you tend to forget to call setCamelContext

A component is much less useful if it doesn't have access to the camel context. And it can cause a few side effects. So we should check that this is set



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

[jira] Resolved: (CAMEL-998) Component should check for camel context is not null

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.

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

Claus Ibsen resolved CAMEL-998.
-------------------------------

    Resolution: Fixed

Also added check in doStart() so if end user have manually created an endpoint and uses eg. createEndpoint with the 3 parameters then the check for camel context provided is bypassed. Now this is in doStart as well so we ensure its there.

> Component should check for camel context is not null
> ----------------------------------------------------
>
>                 Key: CAMEL-998
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-998
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 1.4.0
>            Reporter: Claus Ibsen
>            Assignee: Claus Ibsen
>             Fix For: 1.5.0
>
>
> When creating components manually etc. you tend to forget to call setCamelContext
> A component is much less useful if it doesn't have access to the camel context. And it can cause a few side effects. So we should check that this is set

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