without looking at your code entirely, i don't know what is happening. i just created one simple sample based on cxf's ws-rm sample.
https://www.dropbox.com/s/8fg7bnbwsib95ke/cxf-sample-wsrm-custom-id.tar.gz?dl=0 this file contains sample-wsrm-custom-id.diff - the patch file (the diff to the cxf master) sample-wsrm-custom-id-transcript.txt - the transcription at the server showing the use of the custom id generator 2015-10-22 14:55 GMT+02:00 kupkaj <[email protected]>: > Yes, posted configuration is the same I've tested - using only default bus. > I did some debugging; the probem originates in RMFeature:initializeProvider > method. > bus.getExtension(RMManager.class) eventually invokes > org.apache.cxf.bus.spring.SpringBeanLocator:getBeansOfType(RMManager.class) > and the code in there creates two instances of the type: > > Set<String> s = new > LinkedHashSet<String>(Arrays.asList(context.getBeanNamesForType(type, > > false, > > false))); > s.removeAll(passThroughs); > List<T> lst = new LinkedList<T>(); > for (String n : s) { > lst.add(type.cast(context.getBean(n, type))); // --> creates instance of > spring-configured RMManager > } > lst.addAll(orig.getBeansOfType(type)); // --> creates second instance with > default generator > if (lst.isEmpty()) { > tryOSGI(lst, type); > } > > the latter then replaces first one in bus extensions. > > > > > -- > View this message in context: > http://cxf.547215.n5.nabble.com/WSRM-changing-default-sequence-id-generator-tp5762033p5762131.html > Sent from the cxf-user mailing list archive at Nabble.com.
