Hi Freeman,
He had already tried it twice with 2009.01 and extending
AbstractSoapInterceptor, cleaning out the data/smx directory first just to
make sure there were no leftovers, and it didn't work.
Regards,
Raúl.
Freeman Fang wrote:
>
> Hi Raul,
>
> I believe it should work also with 2009.01 if your interceptor extend
> from AbstractSoapInterceptor.
>
> Freeman
> On 2010-3-16, at 下午9:29, raulvk.soa wrote:
>
>>
>> Hi Freeman,
>>
>> We managed to solve it by making the interceptor extend from
>> AbstractSoapInterceptor and upgrading to 2009.02. There seems to be
>> some
>> kind of bug in 2009.01.
>>
>> Raul.
>>
>>
>> Freeman Fang wrote:
>>>
>>> Hi,
>>>
>>> How you add this interceptor?
>>>
>>> And could you tell me which interceptors invoked and the invoke
>>> sequence?
>>> Freeman
>>> On 2010-3-16, at 上午4:07, raulvk.soa wrote:
>>>
>>>>
>>>> Just to provide a better insight to the problem. We are even
>>>> "browsing" the
>>>> CXF Message and the CXF Exchange:
>>>>
>>>> log.info("Message: " + message.entrySet().toString());
>>>> log.info("Exchange: " +
>>>> message.getExchange().entrySet().toString());
>>>>
>>>> But we don't see any hint of a JBI Message Exchange.
>>>>
>>>> We have checked how the CxfProviderMessageObserver accesses the
>>>> underlying
>>>> JBI Message Exchange, and we have tried the same with no luck:
>>>> message.getExchange().get(MessageExchange.class).
>>>>
>>>> Many thanks again.
>>>>
>>>>
>>>> raulvk.soa wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> We are in the process of migrating from ServiceMix 3.2.2 to
>>>>> ServiceMix
>>>>> 3.3.1, hence migrating from servicemix-cxf-bc-3.2.2 to
>>>>> servicemix-cxf-bc-2009.01.
>>>>>
>>>>> We have a CXF provider which invokes an external Web Service,
>>>>> with an
>>>>> InOut pattern.
>>>>> On the IN Interceptor Chain (response), it has a special
>>>>> interceptor which
>>>>> picks up a header from the message and does some processing on it,
>>>>> injecting the result on the original JBI MessageExchange as a
>>>>> property.
>>>>>
>>>>> We used to be able to access the original JBI MessageExchange with
>>>>> the
>>>>> following:
>>>>>
>>>>> MessageExchange mex = (MessageExchange)
>>>>> message.get(MessageExchange.class);
>>>>>
>>>>> But now it seems to return null always. We have also tried with
>>>>> message.getExchange().get(MessageExchange.class), to no avail.
>>>>>
>>>>> Any idea why this is? The interceptor is initialised with:
>>>>>
>>>>> super(Phase.PRE_INVOKE);
>>>>> addAfter(JbiInWsdl1Interceptor.class.getName());
>>>>>
>>>>> and it extends AbstractPhaseInterceptor<Message>.
>>>>>
>>>>> Many thanks in advance!
>>>>>
>>>>> Raul.
>>>>>
>>>>>
>>>>>
>>>>
>>>> --
>>>> View this message in context:
>>>> http://old.nabble.com/Picking-up-the-MessageExchange-on-a-CXF-Interceptor-tp27909620p27909643.html
>>>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>>>
>>>
>>>
>>> --
>>> Freeman Fang
>>> ------------------------
>>> Open Source SOA: http://fusesource.com
>>>
>>>
>>>
>>
>> --
>> View this message in context:
>> http://old.nabble.com/Picking-up-the-MessageExchange-on-a-CXF-Interceptor-tp27909620p27917779.html
>> Sent from the ServiceMix - User mailing list archive at Nabble.com.
>>
>
>
> --
> Freeman Fang
> ------------------------
> Open Source SOA: http://fusesource.com
>
>
>
--
View this message in context:
http://old.nabble.com/Picking-up-the-MessageExchange-on-a-CXF-Interceptor-tp27909620p27925695.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.
