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

Daniel Galán y Martins updated CAMEL-5308:
------------------------------------------

    Description: 
We are using our own CamelContext, which is extending the DefaultCamelContext. 
Using Main is impossible in this case, since the 
{{getCamelContextMap()}}-method creates statically a DefaultCamelContext. 
Overriding this method doesn't works either, since the field {{registery}} is 
final, and no other accessors are defined.

The given path doesn't breaks existing code bases, and gives an easy possiblity 
to override the context-creation, as well as access to the registry.

  was:
We are using our own CamelContext, which is extending the DefaultCamelContext. 
Using Main is impossible in this case, since the 
{{getCamelContextMap()}}-method creates statically a DefaultCamelContext. 
Overriding this method doesn't works either, since the field {{registery}} is 
final, and no other accessors are defined.



    
> Main is bound to DefaultCamelContext
> ------------------------------------
>
>                 Key: CAMEL-5308
>                 URL: https://issues.apache.org/jira/browse/CAMEL-5308
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.9.2
>         Environment: any
>            Reporter: Daniel Galán y Martins
>         Attachments: Main.java.patch
>
>
> We are using our own CamelContext, which is extending the 
> DefaultCamelContext. Using Main is impossible in this case, since the 
> {{getCamelContextMap()}}-method creates statically a DefaultCamelContext. 
> Overriding this method doesn't works either, since the field {{registery}} is 
> final, and no other accessors are defined.
> The given path doesn't breaks existing code bases, and gives an easy 
> possiblity to override the context-creation, as well as access to the 
> registry.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


Reply via email to