Hi,
AFAIK, the NormalizedMessage content, or "payload" must be always XML,
is a requirement of the JBI spec.
If you can serve your pages in XHTML it could be a good solution, XHTML
is xml compliant.
Salut.
-- Antoni Reus
En/na Stefan Klinger ha escrit:
Hello,
I have built my own lightweight binding components similar to the
o.a.s.components.http.* classes to use with http get in order to
retrieve html pages via ESB. The problem is that the HttpMarshaler/
HttpClientMarshaler expect the content of the http request/ response
body to be xml in order for them to include it in the
NormalizedMessage content. Unfortunately, this does not work with html
as it is not xml compliant, so I put the response body in as an
attachment. I have tested the new components and it seems to work fine.
I wonder whether for a more generic solution the lightweight
Marshalers should support other Mime-Types. Only if the content-type
of the http header is "text/xml" the http requests/ responses are
transformed into the NormalizedMessage contents, otherwise they use an
dummy contents and attach the request/response to the message. I'd be
happy to work on this.
I know that the HttpComponent already allows for MultiMimeMessage Post
Requests, however, it expects at least one part of it to be xml (which
I don't like). I would much rather prefer for the SoapReader to check
if there is a xml part available, if yes, use it as content, otherwise
attach everything and use a dummy message content.
Any comments are most welcome.
Stefan
