JMS configuration redundancy, and what's a sessionPool?

[Benson Margulies <bi...@gmail.com>]

When I configure a JMS endpoint, the code first creates and
initializes an entire JMSConfig object in
org.apache.cxf.transport.jms.JMSOldConfigHolder.configureEndpoint(boolean,
JMSEndpoint), filling options from a number of locations, including
setting concurrency options based on the sessionPool.

All this work is discarded if there is a JMSConfigFeature, since the
feature is not processed until later on.

Shouldn't org.apache.cxf.transport.jms.JMSTransportFactory.getDestination(EndpointInfo)
somehow manage to check for the feature before calling the 'old'
stuff?