XSLT Interface Mapping Not Found For HTTP Response

Question

NW 04's SR 10, RFC => XSL => HTML
The scenario transforms data from R/3 into XML using XSLT and sends it to a 3rd party vendor wrapped inside a field of an HTML form via the HTTPS adapter.  XSL was used for this instead of standard MessageMapping to meet the customer's needed for the XML data to be delivered in an untransformed structure, including their DTD declaration, so they could parse it upon receipt.
The outbound process is successful and the data is posted to the customer's database.  Upon receipt, they send back a simple HTML form containing the success/failure in an H1 tag and our submitted XML data in the Body tag.
The problem is that due to the use of an XSL as the outbound mapping XI does not have a cached message structure to which it can map the response and thus throws the <b>Interface mapping .... does not exist in runtime cache</b> message.  I do not feel this is a cache problem since I've cleared the XI cache, CPACache and anything else I've read as well as verified that the outbound mapping exists in the XI Cache list.  I honestly feel I'm just missing a necessary piece to tell XI how to map the HTML response message back to the RFC Sender.
I have attempted numerous ideas, one of which included the use of the same RFC structure as the inbound and outbound MessageType so that a Response mapping could be specified but a NullPointerException was thrown in the mapping step since the response was of a completely different structure.
My question is how to handle the return data when using XSLT to create the outbound structure dynamically to prevent runtime errors in XI?
Thanks in advance,
Lane

Answer 1

Thanks for the quick response Bhavesh.
I figured out the response mapping option after I posted the question and also thought of using XSL to handle the response but I ran into a few other issues relating to my limited experience with XSLT that is preventing me from completely solving this.
The response is a plain HTML file structured as:
< html >
  < body >
    < h1 >Success/FailureMessage< /h1 >
    < br >
    Record Created
    < br >< br > XML Data: <?xml version="1.0" encoding="utf-8"?><!DOCTYPE ....
  < /body >
< /html >
where the actual XML data posted to the client system is embedded in the HTML body.  Therefore the response is not well-formed XML and fails on parsing but also contains another XML message within the HTML structure that throws off parsing as well.  Do you know XSLT well enough to get around this?
What about writing a Java function that just reads the incoming information but in doing this how do I go about mapping back to the RFC?  Can I get ahold of the XI API somewhere to instantiate the RFC Objects dynamically?
Thanks again,
Lane