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 2010/03/29 12:45:08 UTC

[jira] Commented: (CAMEL-2586) Camel-blueprint component enhancement with an osgi class resolver from camel-osgi

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

Claus Ibsen commented on CAMEL-2586:
------------------------------------

Thanks for your efforts on this one, but its really G Nodet who works on the blueprint stuff.

I am actually not keen that he just copied CamelContextFactoryBean source code, as we do change this class quite often so I do not think his approach is feasible in the future.
I think you should get in touch with Nodet and ask if you can help on his camel-blueprint and work together with him to get it into a quality where we can accept it into the official kit.

> Camel-blueprint component enhancement with an osgi class resolver from camel-osgi
> ---------------------------------------------------------------------------------
>
>                 Key: CAMEL-2586
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2586
>             Project: Apache Camel
>          Issue Type: Improvement
>            Reporter: Johan Edstrom
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 2.3.0
>
>         Attachments: camel-blueprint-osgi-resolv.patch, TypeConverters.patch
>
>
> Simple patch to allow the camel-blueprint namespacehandler resolve components outside the core language.
> This makes it possible to use blueprint and routes such as from:myOwnComponent or from:jms
> in a blueprint like manner along the lines of a spring context.

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