Re: Synchronous RM: lastMessage & offer

[Aki Yoshida <el...@googlemail.com>]

Hi Ben,
I integrated this fix into trunk (2.6.1-SNAPSHOT) and 2.5.x
(2.5.4-SNAPSHOT) some days ago.

Regarding the spring 2.x/3.x incompatibility of the add method that
you mentioned, Dan has already fixed it for 2.5.3.
So, I think you could go to CXF 2.5.x.

Regards, aki

2012/3/22 Ben Pezzei <be...@gmail.com>:
> Hi
>
> @Dan: The 2.5.3 setup was already deleted... so if I remember correctly:
> The SpringBus-class was invoking an add-Method on a spring-class
> during initialization.
> something like beanDefinitionParser.add (the suitable method in 2.5
> may be addProperty).
>
> @Dennis: We found an example in the systest-package: By adding 2 Constants in
> the RequestContext of the client, communication used ws-rm 1.1
> Features/Namespaces.
> The request/response pairs looked ok, afair (But we didnt run the
> whole test-suite due to
> the spring 3 support).
>
> tnx & greetings
> Ben
>
> 2012/3/23 Dennis Sosnoski <dm...@sosnoski.com>:
>> On 03/22/2012 03:37 AM, Ben Pezzei wrote:
>>>
>>> ...
>>>
>>>
>>> It would be very helpfull to have an example of a working config for
>>> WS 1.0 oneway/sync
>>> communication. On the other hand we tried to activate WS RM 1.1 but
>>> unfortunately there
>>> is not much documentation around on how to activate this feature (I
>>> guess changing the namespaces
>>> in the spring config)?
>>
>>
>> Currently you can activate it in the Spring config on the client (the
>> provider automatically adapts to whichever version the client uses). I'm
>> adding the code now to support WS-RM policy configuration instead. I don't
>> think changing to WS RM 1.1 will help with your issues, though.
>>
>>  - Dennis
>>