Bug 759278

Summary:	QpidActivationSpec should be enhanced to use JNDI for ConnectionFactory rather than having to use connectionURL
Product:	Red Hat Enterprise MRG	Reporter:	Weston M. Price <wprice>
Component:	qpid-jca	Assignee:	Weston M. Price <wprice>
Status:	CLOSED DEFERRED	QA Contact:	MRG Quality Engineering <mrgqe-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	Development	CC:	cdewolf, jross, tross
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-20 15:45:11 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description Weston M. Price 2011-12-01 21:14:38 UTC

Similar to the way we allow for looking up Destinations from JNDI for inbound connections, we should allow for this for the connectionFactory we use to create sessions for inbound connectivity. This would allow our clients not to have to provide a connectionUrl on the ActivationSpec which is kludgey and error prone. 

As this is a feature enhancement I am putting it at low priority.

Comment 1 Justin Ross 2012-04-19 17:50:53 UTC

Weston, how much work is this to do?

Comment 2 Weston M. Price 2012-04-19 21:54:43 UTC

 Sorry this one should have really been closed as a 'no fix' awhile ago. Due to pooling considerations from on inbound connections this really doesn't make a lot of sense to do at this time. I just forgot to close it.