So next question. What would make most sense?
Modify wsdlgetinterceptor to not abort chain so the gzip out interceptor can handle request. I was thinking if stax out interceptor executes before wsdl get interceptor the xml writer is already open Then if a wsdl or xsd request I want to avoid executing the soap request stuff. Seems like a big change but is probably reasonably clean approach. Or alternative is to execute gzip out interceptor logic in wsdl get interceptor. On Jul 23, 2013 8:12 PM, "Jason Pell" <ja...@pellcorp.com> wrote: > I checked the code and WSDLGetInterceptor aborts the chain upon handling > of outputting the message, so GZIP Out Interceptor is not going to get a > chance to run. > > > On Tue, Jul 23, 2013 at 8:09 PM, Jason Pell <ja...@pellcorp.com> wrote: > >> The GZIP Out Interceptor does not get executed for the ?WSDL >> >> >> >> >> On Tue, Jul 23, 2013 at 5:43 PM, Aki Yoshida <elak...@gmail.com> wrote: >> >>> not sure but what happens if you put the gzip feature at the service >>> endpoint and send the wsdl query to it with the accept-encoding header >>> set to gzip? >>> >>> 2013/7/23 Jason Pell <ja...@pellcorp.com>: >>> > Is there any way to enable GZIP encoding for the WSDLGetInterceptor? >>> If >>> > not, would it be difficult? >>> >> >> >
