Yes, I can. Besides, the version of xfire server is 1.2.2. This is sample
HTTP message, gotted by sniffer:

POST http://195.64.216.157:8080/fx/xfire/DMSDocuments HTTP/1.1
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; MS Web Services Client
Protocol 2.0.50727.42)
VsDebuggerCausalityData:
uIDPo30IzDAHRfpLuwYfNudOUtgAAAAAcImGxDPbaE+/ug5RPUllJfITBDd3jk9FmyHa6PnI+1cA
CAAA
SOAPAction: ""
Host: 195.64.216.157:8080
Content-Type: multipart/related; type="application/xop+xml";
boundary=--MIMEBoundary633010165949687500;
start="<[EMAIL PROTECTED]>"; start-info="text/xml;
charset=utf-8"
Content-Length: 21674
Expect: 100-continue
Proxy-Connection: Keep-Alive


----MIMEBoundary633010165949687500
content-id: <[EMAIL PROTECTED]>
content-type: application/xop+xml; charset=utf-8; type="text/xml;
charset=utf-8"
content-transfer-encoding: binary

<soap:Envelope xmlns:xop="http://www.w3.org/2004/08/xop/include";
xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xmlns:xsd="http://www.w3.org/2001/XMLSchema";
xmlns:wsa="http://schemas.xmlsoap.org/ws/2004/08/addressing";
xmlns:wsse="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecuri
ty-secext-1.0.xsd"
xmlns:wsu="http://docs.oasis-open.org/wss/2004/01/oasis-200401-wss-wssecurit
y-utility-1.0.xsd"><soap:Header><wsa:Action></wsa:Action><wsa:MessageID>urn:
uuid:adc83434-4b5a-41f8-b03b-b41af02d30a2</wsa:MessageID><wsa:ReplyTo><wsa:A
ddress>http://schemas.xmlsoap.org/ws/2004/08/addressing/role/anonymous</wsa:
Address></wsa:ReplyTo><wsa:To>http://195.64.216.157:8080/fx/xfire/DMSDocumen
ts</wsa:To><wsse:Security><wsu:Timestamp
wsu:Id="Timestamp-05ca3bf6-26f8-43a7-8819-1746cb1e0b3c"><wsu:Created>2006-12
-06T10:43:14Z</wsu:Created><wsu:Expires>2006-12-06T10:48:14Z</wsu:Expires></
wsu:Timestamp></wsse:Security></soap:Header><soap:Body><addFileToDocument
xmlns="http://DMSDocuments.dms.naumen.ru";><documentUUID>corebood0dh780000guj
jjck12f8agag</documentUUID><filename>C:\meat.doc</filename><type>drichnya</t
ype><data><xop:Include href="cid:[email protected]"
/></data></addFileToDocument></soap:Body></soap:Envelope>
----MIMEBoundary633010165949687500
content-id: <[EMAIL PROTECTED]>
content-type: application/octet-stream
content-transfer-encoding: binary

││рб-с






l











----MIMEBoundary633010165949687500--

Sincerely yours, Vadim Gindin
[EMAIL PROTECTED]

-----Original Message-----
From: Tomek Sztelak [mailto:[EMAIL PROTECTED] 
Sent: Thursday, December 07, 2006 6:42 PM
To: [email protected]
Subject: Re: [xfire-dev] Couldn't find MIME boundary
----MIMEBoundary633011127118125000

Can you attach your soap message ?

On 12/7/06, Vadim I. Gindin <[EMAIL PROTECTED]> wrote:
>
>
>
>
> Hello, [email protected]
>
>
>
> I have a problem with using MTOM on xfire server. I have a Documents
> service, that had configured with property "mtom-enabled" setted to true.
>
>
>
> The client of Documents service is a Win32 application, that had wroted on
> C# (.Net Framework 2.0 and Web Services Enhancements 3.0). WSE had turned
on
> for my client project in client mode (and server mode is "optional").
>
>
>
> Here's a code in client, that uses the service.
>
>
>
> DMS.DMSDocumentsWse CategoriesService = new DMS.DMSDocumentsWse();
>
>       CategoriesService.RequireMtom = true;
>
> DMS.DMSCategoryInfo[] Categories =
> CategoriesService.getCategories(Program.settings.folderPath);
>
>
>
> While I'm trying to call getCategories method, I'm getting
> InvalidOperationException, that holds html, containing this message:
>
>
>
> Couldn't find MIME boundary:
> ----MIMEBoundary633011127118125000
>
>
>
> On the server I have got this Exception:
>
>
>
> java.io.IOException: Couldn't find MIME boundary:
> ----MIMEBoundary633011127118125000
>
>       at
>
org.codehaus.xfire.attachments.StreamedAttachments.<init>(StreamedAttachment
s.java:73)
>
>       at
>
org.codehaus.xfire.attachments.StreamedAttachments.<init>(StreamedAttachment
s.java:43)
>
>       at
>
org.codehaus.xfire.transport.http.XFireServletController.invoke(XFireServlet
Controller.java:266)
>
>       at
>
org.codehaus.xfire.transport.http.XFireServletController.doService(XFireServ
letController.java:130)
>
>       at
>
org.codehaus.xfire.transport.http.XFireServlet.doPost(XFireServlet.java:116)
>
>       at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
>
>       at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
>       at
> ru.naumen.fx.servlet.FxServlet$1.execute(FxServlet.java:316)
>
>       at
>
ru.naumen.fx.services.servletlistener.FxServletListenerServiceUtils.handleFx
ServletListenerService(FxServletListenerServiceUtils.java:56)
>
>       at
> ru.naumen.fx.servlet.FxServlet.service(FxServlet.java:258)
>
>       at
> javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
>
>       at
>
org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(Application
FilterChain.java:252)
>
>       at
>
org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterCh
ain.java:173)
>
>       at
>
org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.ja
va:213)
>
>       at
>
org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.ja
va:178)
>
>       at
>
org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126
)
>
>       at
>
org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105
)
>
>       at
>
org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java
:107)
>
>       at
>
org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
>
>       at
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
>
>       at
>
org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConne
ction(Http11Protocol.java:744)
>
>       at
>
org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.jav
a:527)
>
>       at
>
org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWo
rkerThread.java:80)
>
>       at
>
org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.jav
a:684)
>
>       at java.lang.Thread.run(Thread.java:595)
>
>
>
> I have tried to turn off mtom mode on the server and client, but inspite
of
> this there was the same Exception.
>
>
>
> I used the page
> http://www.codeproject.com/soap/MTOMWebServices.asp
>
>
>
> Can anoybody help me in this problem? Any help will be appreciated.
>
>
>
> Sincerely yours, Vadim Gindin
>
> [EMAIL PROTECTED]
>
>


-- 
-----
When one of our products stops working, we'll blame another vendor
within 24 hours.

---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email


---------------------------------------------------------------------
To unsubscribe from this list please visit:

    http://xircles.codehaus.org/manage_email

Reply via email to