Davanum Srinivas' weblog

#1: Apparently a mime boundary like "----_AxIs2_Def_boundary_42214532" is not acceptable, because it has 4 underscores as prefix. WSE wants only 2 underscores.

#2: A long content-type is usually split into multiple lines, but WSE does not like it. it wants the whole thing in one line like this:
Content-Type: multipart/related; boundary=--MIMEBoundary632569798927416768; type="application/xop+xml"; start="cid:0.632569798927416768@example.org"; start-info="text/xml; charset=utf-8"

Someone please point them to the example in the RFC (http://www.faqs.org/rfcs/rfc2387.html)

There are other weird things like for example in the mime part the content-id, content-type are all lower case. which looks odd but is ok.

/me wonders what other hoops the JAX-WS EA folks had to do for getting their interop against 3.0 CTP.