[CXF-1774] JMS Transport: Remove JNDI lookups for ConnectionFactory, targetDestination and replyDestination

• Type: Improvement
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1.2
• Fix Version/s: 2.0.9, 2.1.3
• Component/s: Transports
• Assignee: Christian Schneider
• Reporter: Christian Schneider
• Created: 30/Aug/08 00:55
• Updated: 17/Oct/08 06:08
• Resolved: 29/Sep/08 20:16

Description

Currently you have to configure all jms settings via JNDI. targetDestination is the only config property that already can additionally be configured as a string.

I think the JNDI stuff does not belong into the JMS transport.

ConnectionFactory should simply be configured as a refrence to a bean of type jms ConnectionFactory. So the user of cxf is free to either setup the ConnectionFactory locally or look it up via Spring´s great JNDI support.

The same is true for targetDestination and replyDestination. They should simply be injected. The JNDI logic should be deleted from JMS transport. Additionally it should be possible for targetDestination and replyDestination to set them as simple strings as this is the most common way they will be used by people.

Fixing this will make the JMS Transport code simpler and at the same time the CXF users will get greater flexibility in the configuration.

Issue Links

• is part of: CXF-1832 Third step of Refactoring JMS Transport