You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@servicemix.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2009/02/18 04:36:59 UTC

[jira] Updated: (SMXCOMP-455) Create JbiComponent per SU (camel context)

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

Willem Jiang updated SMXCOMP-455:
---------------------------------

    Summary: Create JbiComponent per SU (camel context)  (was: Create JbiComponent per camel context)

> Create JbiComponent per SU (camel context)
> ------------------------------------------
>
>                 Key: SMXCOMP-455
>                 URL: https://issues.apache.org/activemq/browse/SMXCOMP-455
>             Project: ServiceMix Components
>          Issue Type: Improvement
>            Reporter: Willem Jiang
>             Fix For: servicemix-camel-2009.01
>
>
> Current servicemix-camel component has a short coming of sharing the camel context in the servicemix-camel component.
> It can't create a right camel endpoint for servicemix if there are more than 2 servicemix-camel SU deployed in the container. We need to support looking up the camel-context with the SU name in servicemix-camel component.
> So we need to refactor the servicemix-camel code to pull the camel-jbi component out of servicemix-camel component and make sure there is a new camel-jbi component per camel context ( or per SU).
> In this way the servicemix-camel SU developer could also do some customization of the camel-jbi component per camel context, and the JbiBinding could not be annoying thing for servicemix-camel component.

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