Hi,
Vivek and i agreed that for stream-based attachment decoding there
should be a AttachmentStreamSOAPDecoder that can either inherit from or
delegate to StreamSOAPDecoder for processing the SOAP message part.
We want to use the Boyer More MIME multipart parsing code. For
expediency intially we can buffer the whole message into memory and mark
all parts and create Attachment wrappers. Later we can work out smarter
ways with lazy marking (although since Grizzly buffers the whole message
anyway as long as we can access the byte array there is no need for lazy
marking).
We may need a Decoder factory to create the appropriate Decoder
implementation given the content type. However, the pipeline will also
dictate what Decoder implementation to use e.g. using SAAJ or stream. So
we may need different factories per pipeline configuration.
There can also be an attachment-based XMLStreamReaderEx implementation
that processes XOP infoset. This requires an XMLStreamReader wrapper
that delegates to an underlying XMLStreamReader implementation like SJSXP.
The same XMLStreamReaderEx interface can also be used for FI to return
binary data.
Paul.
--
| ? + ? = To question
----------------\
Paul Sandoz
x38109
+33-4-76188109