Bug 759278 - QpidActivationSpec should be enhanced to use JNDI for ConnectionFactory rather than having to use connectionURL
Summary: QpidActivationSpec should be enhanced to use JNDI for ConnectionFactory rathe...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: qpid-jca
Version: Development
Hardware: All
OS: All
unspecified
low
Target Milestone: ---
: ---
Assignee: Weston M. Price
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-12-01 21:14 UTC by Weston M. Price
Modified: 2016-02-22 00:59 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-04-20 15:45:11 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.