axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ryo Neyama" <>
Subject Re: 10 fresh digits...
Date Thu, 05 Jul 2001 05:03:04 GMT

Also, we need to support charsets handling, right?
XML Media Types are defined in RFC 3023:
The RFC prescribes the way to encode and decode XML including SOAP Envelope
that is transmitted via HTTP transport.   Axis should conform to the RFC for

I think this would be a good opportunity to support XML Media Types because
charset handling is related to MIME stuff.

    Ryo Neyama @ IBM Research, Tokyo Research Laboratory
    Internet Technology

----- Original Message -----
From: "Rob Jellinghaus" <>
To: <>; <>
Sent: Wednesday, July 04, 2001 3:22 AM
Subject: Re: 10 fresh digits...

> At 04:51 PM 6/28/2001 +0100, Axl Mattheus wrote:
> >I am Axl Mattheus from Sun Microsystems' European Software Centre,
> >I'll endeavour to get the SOAP w/Attachments working (as implemented in
> >Apache SOAP 2.2) in Axis.  Any ideas on how that will best fit into Axis'
> >architecture are most welcome!
> Hi Axl!  Welcome!  It would be great to have attachments working.
> Apache SOAP implements attachments via a MIME body class that the message
> gets read into first, with accessors for the various parts of the message.
> Something like that could certainly be done for Axis as well, though Axis
> is written more around a streaming model (parse only the bits you need
> you need them).  It would be great to write the MIME body class using a
> streaming model (i.e. provide streaming access to the first element, then
> the second, etc.).  This would also address Robert Walker's concern
> regarding memory consumption from reading all attachments into memory.
> Perhaps the MIME body class could become a member of the MessageContext,
> and the Message itself would be constructed from the input stream that is
> generated for the first MIME element....
> Also, looking at the Axis ID/HREF code will obviously be crucial for
> attachment support; it'd need to be possible to make an ID / HREF
> to a separate (stream-accessed) part of the MIME message.  I don't know
> exactly how deserialization figures into this picture.
> Glen et al., check me on this?
> As far as how MIME messages are *generated*, I'm less clueful -- I didn't
> look very closely at that part of Apache SOAP.
> A fellow named Jim (can't find his email address, his IRC nick was
> "moatas") said he was looking into attachments, but we haven't heard from
> him in quite a while, so I'd say it's wide open.
> How much time do you have for this?
> Cheers!
> Rob

View raw message