You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Daniel Galán y Martins (JIRA)" <ji...@apache.org> on 2012/05/25 15:12:23 UTC

[jira] [Created] (CAMEL-5308) Main is bound to DefaultCamelContext

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

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


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.



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

       

[jira] [Updated] (CAMEL-5308) Main is bound to DefaultCamelContext

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen updated CAMEL-5308:
-------------------------------

    Priority: Trivial  (was: Major)
    
> 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
>            Assignee: Claus Ibsen
>            Priority: Trivial
>             Fix For: 2.10.0
>
>         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

       

[jira] [Updated] (CAMEL-5308) Main is bound to DefaultCamelContext

Posted by "Daniel Galán y Martins (JIRA)" <ji...@apache.org>.
     [ 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:
------------------------------------------

    Attachment: Main.java.patch
    
> 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.

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

       

[jira] [Resolved] (CAMEL-5308) Main is bound to DefaultCamelContext

Posted by "Claus Ibsen (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CAMEL-5308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Claus Ibsen resolved CAMEL-5308.
--------------------------------

       Resolution: Fixed
    Fix Version/s: 2.10.0
         Assignee: Claus Ibsen

Thanks for the patch.
                
> 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
>            Assignee: Claus Ibsen
>             Fix For: 2.10.0
>
>         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

       

[jira] [Updated] (CAMEL-5308) Main is bound to DefaultCamelContext

Posted by "Daniel Galán y Martins (JIRA)" <ji...@apache.org>.
     [ 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