search

javaee / metro-jax-ws

https://javaee.github.io/metro-jax-ws/
Other
132 stars 68 forks source link

In SOAPMessage mime header Content-Transfer-Encoding mime header is stipped off #855

Open glassfishrobot opened 14 years ago

glassfishrobot commented 14 years ago

Hi All,

All of my SOAP request attachments has "Content-Transfer-Encoding" mime header. In our web service, we have SOAP Message Handler. When I dump the SOAPMessage contents, "Content-Transfer-Encoding" is missing. Below is the code snippet to dump the SOAPMessage.

public boolean handleMessage(SOAPMessageContext context) { SOAPMessage soapMessage = context.getMessage(); soapMessage.writeTo(System.out); We even tried printing all the MIME headers in the attachment, but "Content- Transfer-Encoding" is not present. I thought it was issue on the SAJJ side and opened [https://saaj.dev.java.net/issues/show_bug.cgi?id=52](https://saaj.dev.java.net/issues/show_bug.cgi?id=52) defect. After running snippet provided by Kumar, I found SAJJ is able to parse this header.Hence as suggested by Kumar, I am opening issue. Can you please help us here? PFA: Request dump to webservice: STIRequest.dump soapMessage dump: soapMessage.writeTo.dump Platform details: JAX-WS version: JAX-WS RI 2.2 Container: apache-tomcat-5.5.28 OS: Linux msg-lnx7 2.6.18-164.el5 #1 SMP Tue Aug 18 15:51:48 EDT 2009 x86_64 x86_64 x86_64 GNU/Linux #### Environment Operating System: All Platform: All #### Affected Versions [2.2]
glassfishrobot commented 14 years ago

Reported by nitin_bodke@java.net

glassfishrobot commented 14 years ago

nitin_bodke@java.net said: Created an attachment (id=276) dump of request to webservice

glassfishrobot commented 14 years ago

nitin_bodke@java.net said: Created an attachment (id=277) soapMessage dump in SOAPHandler

glassfishrobot commented 14 years ago

nitin_bodke@java.net said: Hi All, Below is the blog extract which mentions limitation of MimePull parser. "One thought was to make the use of MimePull the default in SAAJ RI, however i heard from the MimePull project lead that one thing it does not handle right now is any kind of non-default Content-Transfer-Encoding (such as base64 for example)." Blog link: http://weblogs.java.net/blog/kumarjayanti/archive/2009/12/10/summary- proprietary-features-saaj-ri-134 Thanks, Nitin

glassfishrobot commented 14 years ago

nitin_bodke@java.net said: JAX-WS team,

Can you please triage this for latest upcoming release?

Thanks, Nitin.

glassfishrobot commented 14 years ago

jitu@java.net said: assigning it to myself.

glassfishrobot commented 14 years ago

jitu@java.net said: JAX-WS always adds Content-Transfer-Encoding: binary to all attachment parts(except of SOAP envelope) while writing the SOAP message.

Are you saying that, if a handler is present, it is not seeing this Content- Transfer-Encoding header in the SOAPMessage object ? Do you have a sample reproducible teestcase ?

glassfishrobot commented 14 years ago

jitu@java.net said: Adding incomplete keyword

glassfishrobot commented 14 years ago

File: soapMessage.writeTo.dump Attached By: nitin_bodke@java.net

glassfishrobot commented 14 years ago

File: STIRequest.dump Attached By: nitin_bodke@java.net

glassfishrobot commented 14 years ago

Was assigned to jitu@java.net

glassfishrobot commented 7 years ago

This issue was imported from java.net JIRA JAX_WS-855