search

ronysebastian / nhin-d

Automatically exported from code.google.com/p/nhin-d
0 stars 0 forks source link

Large MTOM attachments sent via SOAP ending up as 0 byte Documents in XDM package #220

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1.Use SOAP UI to send a request with MTOM attachment of size>100kBytes to a 
running XDR service
2.Inspect Document object received inside XDR service while debugging
3.It comes as an empty object.

What is the expected output? What do you see instead?
All MTOM attachments should be properly received in XDM package

What version of the product are you using? On what operating system?
Direct Project-2.1 deployed in JBoss on Red Hat Linux.

Please provide any additional information below.
MTOM attachments with size approx<50kBytes are received as expected. Issue 
comes only with attachment exceeding approx 100kBytes

Original issue reported on code.google.com by SChauhan...@gmail.com on 11 Jul 2013 at 3:04

GoogleCodeExporter commented 9 years ago 
Issue occurs in Java RI

Original comment by SChauhan...@gmail.com on 11 Jul 2013 at 3:07

GoogleCodeExporter commented 9 years ago 
I was able to resolve this issue by upgrading CXF to 2.4.4 (putting new JARs in 
the "lib" folder of xd.war and removing their corresponding entries from the 
existing set).  All files were obtained from 
http://archive.apache.org/dist/cxf/2.4.4/.  I also modified cxf-servlet.xml, 
inserting the jaxws:properties element, but I don't know if that was relevant 
or if all the sub-elements were specified properly.  See attached for the list 
of files that I inserted, the final list of JARs, and the modified 
cxf-servlet.xml.

See 
http://cxf.apache.org/docs/jax-rs-multiparts.html#JAX-RSMultiparts-Readinglargea
ttachments for my inspiration.

Original comment by EL...@QuadraMed.com on 2 Dec 2013 at 5:22

Attachments: