You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Thomas Diesler (JIRA)" <ji...@apache.org> on 2014/11/03 08:48:33 UTC

[jira] [Reopened] (CAMEL-7969) Container sees Context prematurely (with default name)

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

Thomas Diesler reopened CAMEL-7969:
-----------------------------------

How can this be resolved as won't fix? Again, 3rd party code is called with a partially constructed object. Because the CamelContext instance is only partially constructed it is totally undefined what can be done with it.

I suggest to revisit the Container SPI (starting from requirements) and possibly replace it with something that works.

> Container sees Context prematurely (with default name)
> ------------------------------------------------------
>
>                 Key: CAMEL-7969
>                 URL: https://issues.apache.org/jira/browse/CAMEL-7969
>             Project: Camel
>          Issue Type: Bug
>    Affects Versions: 2.14.0
>            Reporter: Thomas Diesler
>            Assignee: Claus Ibsen
>             Fix For: 2.15.0
>
>
> In the case of SpringCamelContext we have this code
> {code}
>     protected SpringCamelContext createContext() {
>         SpringCamelContext ctx = newCamelContext();        
>         ctx.setName(getId());        
>         return ctx;
>     }
> {code}
> The Container singleton is however called from the DefaultCamelContext ctor (i.e. before the name is initialised properly)
> CrossRef: https://github.com/tdiesler/wildfly-camel/issues/16



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)