Is this exactly showing your spring configuration with regard to the
bus setting?

I think if you have the bus configured exactly in that way, the bus
will be used as the default cxf bus and it should be injected to your
rmManager instance and subsequently the RMFeature should find this
rmManager. If you have several buses, you will need to assign the
particular bus an explicit reference so that the two things can be
wired.
e.g.
<wsrm-mgr:rmManager xmlns:wsrm-mgr="http://cxf.apache.org/ws/rm/manager";>
      <property name="bus" ref="bus"/>
      ...
</wsrm-mgr:rmManager>
<cxf:bus bus="bus">
...
</cxf:bus>

2015-10-22 7:33 GMT+02:00 kupkaj <[email protected]>:
> Yes, this part is pretty straightforward, but I don't know how to configure
> RM feature to use my RMManager.
>
> So far I came up with this configuration
>
>     <cxf:bus>
>         <cxf:features>
>             <cxf:logging/>
>             <wsa:addressing/>
>             <wsrm-mgr:reliableMessaging/>
>         </cxf:features>
>
>     </cxf:bus>
>
>         <wsrm-mgr:rmManager 
> xmlns:wsrm-mgr="http://cxf.apache.org/ws/rm/manager";>
>       <wsrm-policy:RMAssertion>
>           <wsrm-policy:BaseRetransmissionInterval Milliseconds="4000"/>
>           <wsrm-policy:AcknowledgementInterval Milliseconds="2000"/>
>       </wsrm-policy:RMAssertion>
>             <wsrm-mgr:sourcePolicy>
>                 <wsrm-mgr:sequenceTerminationPolicy maxLength="5"/>
>             </wsrm-mgr:sourcePolicy>
>             <property name="idGenerator" ref="idGenerator"/>
>         </wsrm-mgr:rmManager>
>
>     <bean id="idGenerator" class="demo.wsrm.SequenceIdGenerator"/>
>
> but it's not working. It creates instance of RMManager that uses my
> generator and stores in on bus, but initialization of RM feature replaces
> this instance with new one, which uses default generator.
>
>
>
> --
> View this message in context: 
> http://cxf.547215.n5.nabble.com/WSRM-changing-default-sequence-id-generator-tp5762033p5762118.html
> Sent from the cxf-user mailing list archive at Nabble.com.

Reply via email to