Bug 778891 (SOA-1333)

Summary: JMSRouter should accept extended JNDI configuration parameters
Product: [JBoss] JBoss Enterprise SOA Platform 4 Reporter: Kevin Conner <kevin.conner>
Component: JBossESBAssignee: Kevin Conner <kevin.conner>
Status: CLOSED NEXTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 4.3 CP01   
Target Milestone: ---   
Target Release: 4.3 CP02   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-1333
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-16 11:06:23 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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