jax ws - Rewriting "Content-Type" header and MIME boundaries with JAX-WS and MTOM/XOP -
i have specification need comply with, makes rather unusual demands (for historical reasons) when providing , using web service using mtom/xop:
to summarize, content-type http header has coded this: start-info , action have coded separate parameters of content-type: start-info="application/soap+xml";action="urn:ihe:iti:2007:retrievedocumentset"
- while in contrast that, mtom/xop specification demand this:
content-type: multipart/related;start="...";type="application/xop+xml";boundary="...";start-info="application/soap+xml;action=\"urn:ihe:iti:2007:retrievedocumentset\""
- so "action" included , escaped within "start-info" parameter. using jax-ws provide , consume web service, , cannot see working solution changing headers , mime boundaries meet specification's demands.
the same applies mime boundaries sent web service message.
java7 , java8's included jax-ws implementation seem handle differently, i.e.: java7 encoding expected specification need comply with, while java8 according mtom/xop specification. cannot go java8 because other libraries using need java8
is there way of modifying jax-ws's behaviour, or of intercepting , changing headers / mime boundaries before reaching other system?
meanwhile, found answer: possible use custom tubefactory in application. can return standard httptransportpipe modified codec implementation, modifies content-type header in getstaticcontenttype(packet) method.
Comments
Post a Comment