XML not well formed - Java Mapping, Webservice to RFC Scenario

Question

Hello All Experts,
I have facing a strange type of error. I have written a Java Mapping which implements a DOM parser to take a request from a Webservice and validate it on the basis of some prerequisites. i.e. If data in the incoming request is valid, it creates a message of the same structure type as the input. If the incoming data is incorrect or incomplete; It generates an Error response structure.
When I run and test the same mapping program using Editplus Java editor for the error scenario; it executes perfectly and creates the correct error XML structure. (I checked it by importing the structure in the XI Message mapping test tab). But when I create jar of my java mapping program and test it in my interface mapping, it gives me "XML not well formed error" (Problem while building the tree).
Any idea as to why is it behaving in such a way? There are 2 reasons which come to my mind as of now:
1. The initilization of my input and output streams in the public static void main:
            InputStream in = new FileInputStream(new File("Input.xml"));
           OutputStream out = new FileOutputStream(new File("Output.xml"));
           validateXML myMapping = new ValidateXML();
            myMapping.execute(in, out);
The Output.xml has the xml structure for the correct case, do I have to initialize my outputstream for the error file? say error.xml
2. My Webservice interface is a sychronous interface (Request / Response) and output of the Java mapping program are two asynchronous interface. (I'll use a synch-asynch bridge when this works) - Is that causing a problem?
Please help.
Best regards,
Varun

Answer 1

Hello Varun,
it gives me "XML not well formed error" (Problem while building the tree).
I have come across the same error message while testing in interface mapping. My problem was when an exception occured in java mapping, the execution terminates with the messages XML not well formed error". In order to solve this issue what i did was catch the exception type TransformerException and in that catch block throw StreamTransformationException exception in main methos of mapping program i.e execute().
eg:-                                                                               
catch (TransformerException e) {
               throw new StreamTransformationException("Can not write XML.", e);
By doing this you will see the exception raised , because some times when you execute your mapping with mail() method, though it create the file, when you try to open it will give error if any exceptions occured in mapping. By using the above notation you can handle those in java mapping.
Hope you have gone through this blog.
[Handling and Tracing Exceptions in java mapping|http://www.sdn.sap.com/irj/scn/weblogs;jsessionid=(J2EE3417700)ID1055371050DB01666765031379427182End?blog=/pub/wlg/15061]
Regards,
Prasanna