Bug 735384

Summary:	Qpid JCA Adapter -- ActivationSpec property ClientID non-standard
Product:	Red Hat Enterprise MRG	Reporter:	Weston M. Price <wprice>
Component:	qpid-jca	Assignee:	messaging-bugs <messaging-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	low
Version:	2.0	CC:	astitcher, cdewolf, iboverma, jpechane, tross
Target Milestone:	2.1.2
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-12-07 17:43:30 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Weston M. Price 2011-09-02 14:42:07 UTC

As per the JCA specification, the recommended JMS ActivationSpec property

clientId 

does not match the QpidActivationSpec property 

ClientID

Some application servers, most notably Geronimo follow the recommendations to the letter. As such, with the new example code, which includes a Topic example, this will not deploy correctly in Geronimo. We need to modify this property to be in line with the JMS ActivationSpec recommendation. 

This needs to be modified in ra.xml, as well as on the implementation classes.

Comment 1 Andrew Stitcher 2011-09-22 13:30:51 UTC

This has been fixed in package qpid-java-jca-0.10-10