#10 RFC 822 Header Parsing broken

[Henner Zeller]

Hi,
(I've sent this patch to the mailing list in November
24th, but it hasn't been incorparated yet).

In an attempt to implement Beep as a protocol for JAXM
and SAAJ using the
SOAP Profile specification, I noticed, that the
implementation of the
RFC822 Header parser has not been complete.

The problems arises when sending attachments with SUNs
default
implementation of JAXM. When sending an Attachment with
Soap, the payload
actually contains a full mime multipart document, so
one mime header
of a beep message contains the boundary which happens
to be on a new line
with the SUN implementation; something like:

Content-Type:multipart/related; type="text/xml";
boundary="----=_Part_0_19610963.1069622873839"

This is correct according to RFC822 (Paragraph 3.2,
field-body
production), but is not implemented in the Beep header
parser which does
not understand multiline headers. So in this case the
boundary is lost and
SOAP-Attachments won't work :-(

I fixed this for the current CVS by implementing a
RFC822 parser (an
improved version found on w3c)

The patch can be found in the attachment.
It will create a new java file and a patch file:

rfc822-header-parse.patch
src/org/beepcore/beep/util/Rfc822HeaderParser.java

The files can then be patched with
patch -p0 < rfc822-header-parse.patch

With this patch, sending JAXM Attachments works without
problems.

ciao,
-hen

[Henner Zeller]

Tar file with new file and patch