Re: [ebxmlms-develop] Problems with MIME headers on error messages

[Bob K. <py...@ce...>]

I have just fixed the bug and committed it to CVS. (Include adding unit 
test case)
However, since the sourceforge's CVS doesn't work quite stable (when I 
commit, I see that it cannot generate acknowledgment to the mailing 
list... and from previous experience, the user may not checkout the 
latest version just after I committed), therefore you may not able check 
it out from CVS.

Thanks for reporting those bugs.

Regards,
Bob Koon

Mayne, Peter wrote:

> I'm using Hermes pulled from CVS this morning.
>
> When I receive an error message, Hermes couldn't build the bytes into 
> a SOAP message. I tracked this down to 
> EbxmlMessage.getMessageFromDataSource(), which contains:
>
>             /*
>             final MimeHeaders headers = new MimeHeaders();
>             headers.addHeader(Constants.CONTENT_TYPE, 
> Constants.TEXT_XML_TYPE);
>             */
>             final MimeHeaders headers = parsedOutput.getMimeHeaders();
>
> It seems that parsedOutput.getMimeHeaders() doesn't work properly: it 
> wasn't producing any headers, so building the SOAP message was failing 
> with a "no content-type" exception.
>
> Going back to the predefined header by switching the comments around:
>
>             final MimeHeaders headers = new MimeHeaders();
>             headers.addHeader(Constants.CONTENT_TYPE, 
> Constants.TEXT_XML_TYPE);
>             /*
>             final MimeHeaders headers = parsedOutput.getMimeHeaders();
>             */
>
> now the message builds properly.
>
> PJDM
> -- 
> Peter Mayne
> Technology Consultant
> Spherion Technology Solutions
> Level 1, 243 Northbourne Avenue, Lyneham, ACT, 2602
> T: 61 2 62689727  F: 61 2 62689777
>
>  
>
>
>  
>