cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jason Pell <ja...@pellcorp.com>
Subject Re: Controlling mtom using client headers.
Date Mon, 11 Aug 2014 23:07:26 GMT
If any other devs have info on why this is not enabled and a recommendation
for where I could add this code either to existing interceptor or use my
new one.

I tried using this interceptor on incoming chain but seems out going
message gets properties from exchange only.
On 11/08/2014 2:22 PM, "Jason Pell" <jason@pellcorp.com> wrote:

> In the mean time I created an interceptor to override the mtom-enabled
> property based on the Accept property.  I would prefer to use something
> build into cxf, but this seems to work for my use case.
>
>
> https://github.com/pellcorp/cxf/blob/master/JavaFirst/src/main/java/com/pellcorp/server/interceptor/MtomOutInterceptor.java
>
>
>
>
> On Mon, Aug 11, 2014 at 12:47 PM, Jason Pell <jason@pellcorp.com> wrote:
>
>> I cant seem to find code that controls mtom based on what a client can
>> handle. My understanding is the Accept header should be used. If I have a
>> Accept header which is either a wild card or includes application/xop+xml
>> use mtom if con figured on endpoint otherwise fall back to inlined base 64.
>>
>> I tried this and it did not work. I am very surprised this is not
>> working. Perhaps I am missing something.
>>
>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message