Hmm, SwA with dime must be rather uncommon (as SwA itself is nowadays), as I can only google one reference to it wth CXF from 2009 saying that it's not supported: http://cxf.547215.n5.nabble.com/soap-with-attachments-mime-dime-tp568705p568708.html

Since you own the SOAP service (and hence the WSDL), any chance you can dictate the more modern MTOM as the transmission mechanism: http://www.jroller.com/gmazza/entry/using_mtom_and_apache_fop ?

Glen

On 09/12/2012 12:01 AM, arunviswa wrote:
Hi,

I've implemented the SOAP web service using Apache-CXF 2.6.
One of my client is sending the binary data using the Content-Type
"application/dime".

This request is failing with the SoapFault "Error reading: XML Stream
Reader" from the ReadHeadersInterceptor.

Following is the Stack trace of the error:

Fault Message = Error reading XMLStreamReader.
org.apache.cxf.binding.soap.SoapFault: Error reading XMLStreamReader.
        at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:237)
        at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:60)
        at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:263)
        at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:118)
        at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:318)
        at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.doService(JettyHTTPDestination.java:286)
        at
org.apache.cxf.transport.http_jetty.JettyHTTPHandler.handle(JettyHTTPHandler.java:72)
        at
org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:936)
        at
org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:873)
        at
org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:117)
        at
org.eclipse.jetty.server.handler.ContextHandlerCollection.handle(ContextHandlerCollection.java:247)
        at
org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
        at org.eclipse.jetty.server.Server.handle(Server.java:346)
        at
org.eclipse.jetty.server.HttpConnection.handleRequest(HttpConnection.java:581)
        at
org.eclipse.jetty.server.HttpConnection$RequestHandler.content(HttpConnection.java:1057)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:899)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:214)
        at 
org.eclipse.jetty.server.HttpConnection.handle(HttpConnection.java:411)
        at
org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:526)
        at
org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:41)
        at
org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:528)
        at java.lang.Thread.run(Thread.java:662)
Caused by: javax.xml.stream.XMLStreamException: ParseError at
[row,col]:[1,1]
Message: Content is not allowed in prolog.
        at
com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.next(XMLStreamReaderImpl.java:594)
        at
com.sun.org.apache.xerces.internal.impl.XMLStreamReaderImpl.nextTag(XMLStreamReaderImpl.java:1235)
        at
org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:138)
        ... 21 more


So following is my queries:
1. Does apache cxf supports the "applcation/dime" content type messages ?
2. If it supports how does it determine the SoapMessage from the DIME
message? or I need to write an interceptor to parse the DIME message to get
the SOAP message?, SoapAttachmentInterceptor won't do this ?

Thanks In Advance,
Arun



--
View this message in context: 
http://cxf.547215.n5.nabble.com/Does-Content-Type-application-Dime-support-in-Apache-CXF-2-6-tp5713850.html
Sent from the cxf-user mailing list archive at Nabble.com.


--
Glen Mazza
Talend Community Coders - coders.talend.com
blog: www.jroller.com/gmazza

Reply via email to