You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@cxf.apache.org by Alessio Soldano <as...@redhat.com> on 2014/03/07 16:35:30 UTC
WS-RM and WSDLGetInInterceptor
Hi,
I'm seeing the exception at [1] when getting the published WSDL for an
endpoint using WS-RM (policy).
The reason seems to be the lack of WSAddressing MAP in that case,
possibly related to the modified interceptor chain being executed when a
wsdl GET is processed. I believe the RM interceptor should not be run at
all when wsdl GET requests are processed, but wanted to check here too.
And if that's the proper approach for solving the problem, should I add
it in WSDLGetInInterceptor::cleanUpOutInterceptors ?
Thanks
Alessio
[1] http://www.fpaste.org/83382/13942061/raw/
--
Alessio Soldano
Web Service Lead, JBoss
Re: WS-RM and WSDLGetInInterceptor
Posted by Aki Yoshida <el...@gmail.com>.
Hi Alessio,
People thank you for spotting this error :-)
I just integrated the fix to 2.7.x.
regards aki
2014-03-10 15:14 GMT+01:00 Alessio Soldano <as...@redhat.com>:
> Thanks Aki, just seen your commit :-)
>
>
> On 10/03/14 11:20, Aki Yoshida wrote:
>>
>> Hi Alessio,
>> Just look at the code and I think the problem s the
>> RMDeliveryInteceptor sometimes gets inserted behind
>> OutputGoingInterceptor, as it only specifies the phase condition and
>> not the before condition. I think using the correct rule should fix
>> this issue.
>> I can look at it to see if that's indeed the case and fix it in that case
>> there.
>> regards, aki
>>
>> 2014-03-07 16:35 GMT+01:00 Alessio Soldano <as...@redhat.com>:
>>>
>>> Hi,
>>> I'm seeing the exception at [1] when getting the published WSDL for an
>>> endpoint using WS-RM (policy).
>>> The reason seems to be the lack of WSAddressing MAP in that case,
>>> possibly
>>> related to the modified interceptor chain being executed when a wsdl GET
>>> is
>>> processed. I believe the RM interceptor should not be run at all when
>>> wsdl
>>> GET requests are processed, but wanted to check here too. And if that's
>>> the
>>> proper approach for solving the problem, should I add it in
>>> WSDLGetInInterceptor::cleanUpOutInterceptors ?
>>> Thanks
>>> Alessio
>>>
>>> [1] http://www.fpaste.org/83382/13942061/raw/
>>>
>>> --
>>> Alessio Soldano
>>> Web Service Lead, JBoss
>>>
>
>
> --
> Alessio Soldano
> Web Service Lead, JBoss
>
Re: WS-RM and WSDLGetInInterceptor
Posted by Alessio Soldano <as...@redhat.com>.
Thanks Aki, just seen your commit :-)
On 10/03/14 11:20, Aki Yoshida wrote:
> Hi Alessio,
> Just look at the code and I think the problem s the
> RMDeliveryInteceptor sometimes gets inserted behind
> OutputGoingInterceptor, as it only specifies the phase condition and
> not the before condition. I think using the correct rule should fix
> this issue.
> I can look at it to see if that's indeed the case and fix it in that case there.
> regards, aki
>
> 2014-03-07 16:35 GMT+01:00 Alessio Soldano <as...@redhat.com>:
>> Hi,
>> I'm seeing the exception at [1] when getting the published WSDL for an
>> endpoint using WS-RM (policy).
>> The reason seems to be the lack of WSAddressing MAP in that case, possibly
>> related to the modified interceptor chain being executed when a wsdl GET is
>> processed. I believe the RM interceptor should not be run at all when wsdl
>> GET requests are processed, but wanted to check here too. And if that's the
>> proper approach for solving the problem, should I add it in
>> WSDLGetInInterceptor::cleanUpOutInterceptors ?
>> Thanks
>> Alessio
>>
>> [1] http://www.fpaste.org/83382/13942061/raw/
>>
>> --
>> Alessio Soldano
>> Web Service Lead, JBoss
>>
--
Alessio Soldano
Web Service Lead, JBoss
Re: WS-RM and WSDLGetInInterceptor
Posted by Aki Yoshida <el...@gmail.com>.
Hi Alessio,
Just look at the code and I think the problem s the
RMDeliveryInteceptor sometimes gets inserted behind
OutputGoingInterceptor, as it only specifies the phase condition and
not the before condition. I think using the correct rule should fix
this issue.
I can look at it to see if that's indeed the case and fix it in that case there.
regards, aki
2014-03-07 16:35 GMT+01:00 Alessio Soldano <as...@redhat.com>:
> Hi,
> I'm seeing the exception at [1] when getting the published WSDL for an
> endpoint using WS-RM (policy).
> The reason seems to be the lack of WSAddressing MAP in that case, possibly
> related to the modified interceptor chain being executed when a wsdl GET is
> processed. I believe the RM interceptor should not be run at all when wsdl
> GET requests are processed, but wanted to check here too. And if that's the
> proper approach for solving the problem, should I add it in
> WSDLGetInInterceptor::cleanUpOutInterceptors ?
> Thanks
> Alessio
>
> [1] http://www.fpaste.org/83382/13942061/raw/
>
> --
> Alessio Soldano
> Web Service Lead, JBoss
>