Hi,

I'd suggest you use cxf bc instead which have better MTOM support.

Freeman

On 2012-2-1, at 下午6:32, MarekSvitok wrote:

Hello.

We're using servicemix 4.4.0. We'd like to provide .Net service which uses
xop+xml soap messages.
I have defined http:soap-provider like this :

<http:soap-provider wsdl="https://spczapp00022:8080/messagebox?wsdl";
locationURI="https://spczapp00022:8080/messagebox "
                       service="msgboxns:MessageBoxService"
                       endpoint="CustomBinding_IMessageBoxService"
                       validateWsdl="false">

       <http:ssl>
           <http:sslParameters keyStore="/LocalKeystore/.keystore"
                               keyStorePassword="******"
                               keyPassword="******"
                               trustStore="/LocalKeystore/.keystore"
                               trustStorePassword="********"/>
       </http:ssl>
   </http:soap-provider>

I'm still getting com.ctc.wstx.exc.WstxUnexpectedCharException: Unexpected character '-' (code 45) in prolog; expected '<' exception. It's cause by the
multipart soap message from the .Net. Wsdl includes wsdl:policy -
<wsoma:OptimizedMimeSerialization

xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization "/>

I'd like to define http:policies parameter for my http:soap- provider, but I
don't know how. I tried this :

<http:policies>
    *<wsoma:OptimizedMimeSerialization

xmlns:wsoma="http://schemas.xmlsoap.org/ws/2004/09/policy/optimizedmimeserialization "/>*
</http:policies>

with no success : Unrecognized xbean namespace mapping

Please help.
Thank you in advance.
Mark

--
View this message in context: 
http://servicemix.396122.n5.nabble.com/XOP-policy-within-http-soap-provider-tp5447119p5447119.html
Sent from the ServiceMix - User mailing list archive at Nabble.com.

---------------------------------------------
Freeman Fang

FuseSource
Email:[email protected]
Web: fusesource.com
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com









Reply via email to