Bug 778891 (SOA-1333) - JMSRouter should accept extended JNDI configuration parameters
Summary: JMSRouter should accept extended JNDI configuration parameters
Keywords:
Status: CLOSED NEXTRELEASE
Alias: SOA-1333
Product: JBoss Enterprise SOA Platform 4
Classification: JBoss
Component: JBossESB
Version: 4.3 CP01
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.3 CP02
Assignee: Kevin Conner
QA Contact:
URL: http://jira.jboss.org/jira/browse/SOA...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-05-26 11:46 UTC by Kevin Conner
Modified: 2009-09-16 11:06 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-09-16 11:06:23 UTC
Type: Bug

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


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SOA-1333 0 None None None Never

Description Kevin Conner 2009-05-26 11:46:56 UTC 
Date of First Response: 2009-07-23 03:14:24
project_key: SOA
Comment 1 Kevin Conner 2009-05-26 11:47:34 UTC 
Link: Added: This issue is related to JBESB-2555
Comment 2 Kevin Conner 2009-05-26 11:54:10 UTC 
Link: Removed: This issue is related to JBESB-2555
Comment 3 Kevin Conner 2009-05-26 11:55:22 UTC 
Link: Added: This issue depends JBESB-2591
Comment 4 Dana Mison 2009-07-23 07:14:24 UTC 
added to 4.3.CP02 release notes as resolved:

JBESB-2555 - JMSRouter nows accepts extended JNDI configuration parameters.
Comment 5 Kevin Conner 2009-09-16 10:40:54 UTC 
This allows JMSRouter to accept JNDI properties with provider specific prefixes, it should now be possible to use JMSRouter with those providers.
Comment 6 Kevin Conner 2009-09-16 11:06:23 UTC 
Changes are present
Note You need to log in before you can comment on or make changes to this bug.