Bug 973086 - Component properties does not work when more than one Camel implementation is present
Summary: Component properties does not work when more than one Camel implementation is...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: JBoss Fuse Service Works 6
Classification: JBoss
Component: SwitchYard
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Rob Cernich
QA Contact: Matej Melko
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-06-11 09:20 UTC by Jiri Pechanec
Modified: 2025-02-10 03:27 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-02-10 03:27:55 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SWITCHYARD-2144 0 Critical Resolved SwitchYardPropertiesParser does not work for multiple Components 2015-04-13 20:28:41 UTC

Description Jiri Pechanec 2013-06-11 09:20:01 UTC
SwitchYard uses internally one CamelContext.

When a Camel component is activated in org/switchyard/component/camel/deploy/CamelActivator it sets PropertiesParser for Camel Properties Component. The problem is that this setting is global for the single shared CamelContext. So if there are two or more Camel implementations, then the PropertiesParser is set for each of them effectively overriding previous setting. This ensures that Camel implementations shares properties from the last Camel implementation that was activated.

Comment 1 Rob Cernich 2014-10-21 18:34:40 UTC
Hey Kevin, I don't think we can address this issue in the code.  At best, we should document that names of properties specified for camel components must be unique throughout the application.  WDYT?

Comment 2 JBoss JIRA Server 2014-12-15 17:41:02 UTC
Rob Cernich <rcernich> updated the status of jira SWITCHYARD-2144 to Resolved

Comment 3 Rob Cernich 2014-12-15 17:42:25 UTC
I'm n'ack'ing this as we cannot isolate Camel's property resolver to specific components (i.e. we either can't or don't know how to fix this).

Comment 4 Len DiMaggio 2015-02-17 17:36:32 UTC
Nacking this bugzilla - this is an EAP issue and FSW 6.2 will not embed EAP.

Comment 5 Ken Johnson 2015-03-12 18:26:06 UTC
Does this change with the camel-wildfly subsystem?
Will SwitchYard 2 on EAP 6.4 use camel-wildfly modules?

If this bug is unaffected by camel-wildfly, I will nack for now.

Comment 6 tcunning 2015-04-01 15:38:43 UTC
This should not be affected by camel-wildfly.   In the SwitchYard ER2 submission, we will be reusing the camel-wildfly modules (commit is already in).

Comment 12 Red Hat Bugzilla 2025-02-10 03:27:55 UTC
This product has been discontinued or is no longer tracked in Red Hat Bugzilla.


Note You need to log in before you can comment on or make changes to this bug.