axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 17664] - SOAPMessage MimeHeaders not being created for attachments
Date Wed, 05 Mar 2003 17:46:25 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17664>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17664

SOAPMessage MimeHeaders not being created for attachments





------- Additional Comments From hags@metahusky.net  2003-03-05 17:46 -------
Ok, now you're starting to scare me (we're planning to use Axis for our
live/public system.)

(After all you don't have javax.activation.DataHandler in Axis CVS either, but
that doesn't seem to stop you from using it in the SOAP implementations.)

Anyhow, I realise that the Axis SOAP implementation is rather strangely lacking
in many of the javax areas, which makes it hard to understand how it could be
directly considered a replacement for Sun's reference implementation.  But you
can pull the JAXMServlet class direct from the Sun JAXM Reference implementation
from a download at 

http://java.sun.com/xml/javaxmlpack.html

All of this is rather irrelevant really, just create a SOAPMessage with
attachments and try to generate a raw valid multipart reply to a SOAP request
using only the SOAPMessage API (which is what a JAXMServlet would have to be
able to do) and you'll see its not possible, the necessary header information is
just not available to you under Axis.  This makes it impossible to cleanly
implement a SOAP server without nasty Axis specific hacks.

If you wish I'll provide you with an example like the one already submitted but
doesn't depend on the JAXMServlet.  Let me know if you'd like this.

Mime
View raw message