cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christian Schneider <>
Subject [jms] Heads up removal of old config style in cxf jms transport
Date Tue, 25 Feb 2014 14:29:12 GMT
Hi all,

like planned I will now start to remove the old wsdl and spring conduit 
/ destination config style.
I originally planned to keep the JMSConfiguration style which was set 
using the JMSConfigFeature. During the refactorings I found though
that the new JMSEndpoint will have to provide all important elements of 
JMSConfiguration anyway. The spec allows to add these as custom 
properties which I did.

So I wonder if it would make sense to only keep the spec based URI and 
WSDL config?
For people who like Java pojo based configs we could allow to set a 
JMSEndpoint in the config as a replacement for the JMSConfiguration 
style. What do you think?

If no one objects I will also remove the JMSConfigFeature based config 

For reference here are some pointer to the new config style:;a=blob_plain;f=rt/transports/jms/src/main/java/org/apache/cxf/transport/jms/uri/;hb=HEAD

Some examples of jms endpoint uris:;a=blob_plain;f=rt/transports/jms/src/test/java/org/apache/cxf/transport/jms/uri/;hb=HEAD

This shows the new config uris with jndi based connection factory as 
well as with context based connection factory (e.g. blueprint or spring):;a=blob_plain;f=rt/transports/jms/src/test/java/org/apache/cxf/transport/jms/uri/;hb=HEAD

This is the jms spec test suite which shows many different spec based 
config variants:;a=blob_plain;f=testutils/src/main/resources/wsdl/jms_spec_testsuite.wsdl;hb=HEAD


Christian Schneider

Open Source Architect

View raw message