From Traditional Integration to Composition – Enterprise Business Services - Applied SOA Patterns on the Oracle Platform - page 248

XDIMessageHelper msghelper = new XDIMessageHelper();
try
{
//Oracle parser
msgXdiDOM = msghelper.getmsgXdiasDOM(getReader());
}
catch(Exception ex) {
logger.log( "ERR", "Unable to parse incoming
message", "N/A", "N/A", XDIServlet.servletInstance + "
Front Controller", "N/A", "3" );
ack.setackMessageStatusCode(ack.STATUS_CRITICAL_ERROR);
ack.setackEventCode(ack.STATUSCODE_CRITICAL_ERROR);
ack.setackEventDescription(ex.toString());
ex.printStackTrace();
}
return msgXdiDOM;
}
......
// In XDIMessageHelper. Actual parsing
//Technically you can use any DOM parser. We use classic
oracle.xml.parser.v2.* It's also configurable through
Servlets initiation
public XMLDocument getmsgXdiasDOM(java.io.Reader
reader)
throws IOException, SAXParseException, SAXException
{
XMLDocument msgXdiDOM = OraXMLHelper.parse(reader,
null);
return msgXdiDOM;
}
As you have noticed, we are populating the Acknowledge object (passing the ack
parameter) every time when it's necessary, and definitely in case of errors. We will do ex-
actly the same with MessageHeader , right after obtaining the DOM message:
// set Message header values
helper.setMessageHeader(msgXdiDOM, mheader, ack);