RE: Factory.Parse issue

[Lawrence Jones]

Title: Factory.Parse issue

Hi Jason   When you say the program “craps out”, what exactly do you see? And what do you means by “running the jar”? Do you mean running a java process from the command line with the jar on the classpath?   Cheers,   Lawrence   From: Green, Jason M. [mailto:[EMAIL PROTECTED] Sent: Monday, April 03, 2006 12:27 PM To: dev@xmlbeans.apache.org Subject: Factory.Parse issue   Hey everyone. I'm having an odd issue with xmlbeans.  When using it while developing in my IDE, it seems to work fine.  When actually running the jar (at least along those lines), the program craps out on the Factory.parse method.  We pass in a ByteArrayInputStream, and like I say, it works like a charm when running from our IDE.  The big problem is, there is absolutely no output to our files or anything saying why.  We created our jar with -debug, but don't know where the output is thrown to.  We have traced it down to here but can't track it past here: This is in the PlanListDocumentDocument1$Factory.java file public static PlanListDocumentDocument1 parse(InputStream inputstream, XmlOptions xmloptions)         throws XmlException, IOException     {         return (PlanListDocumentDocument1)XmlBeans.getContextTypeLoader().parse(inputstream, PlanListDocumentDocument1.type, xmloptions);     } Here is the line of code that we call: ResponseDocumentDocument1 response = ResponseDocumentDocument1.Factory.parse(new ByteArrayInputStream(result)); So basically, here's my main question.  If you set the debug, is the debug just sent to standard out, or can it be logged?  Sorry for how much this post jumps around.  We're kinda frazzled here. Jason _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.