Bug 973086

Summary:	Component properties does not work when more than one Camel implementation is present
Product:	[JBoss] JBoss Fuse Service Works 6	Reporter:	Jiri Pechanec <jpechane>
Component:	SwitchYard	Assignee:	Rob Cernich <rcernich>
Status:	ASSIGNED ---	QA Contact:	Matej Melko <mmelko>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.0.0	CC:	kejohnso, ldimaggi, rcernich, soa-p-jira, tcunning
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	If you activate a Camel component, it sets the component properties. If there is more than one Camel implementation, the component properties set for each Camel component effectively overrides the previous setting.	Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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