Re: Re: Xmlc: error reporting (was : martin fowler and jsp evils...)

On Tuesday 14 January 2003 17:14, dcorbin@xxxxxxxxxxxxxx wrote:
> > Hi All,
> >
> > So, I'm hoping to get Martin on board with xmlc and the value of
> > DOM-based presentation development.  Seeing the posting about
> > http://xmlceclipse.sourceforge.net really pumped me up.  This community
> >  needs folks to beat the drum and get the word out.  xmlc is still one
> > of  the best kept secrets out there.
>
> Yes.  As the primary developer of this plugin, let me take the opportunity
> to plead for more help!  I know we're all juggling lot of balls, but any
> help would be appreciated.
> I have a specific question, and I have not *recently* delved into the XMLC
> source.  It seems to me the last time I was there, that errors/warnings
> when compiling XMLC where shot straight to stderr without any higher-level
> mechanism.  Is this correct?  

Mostly. By default, the error messages are output to stderr, but they can be 
easily redirected to an arbitrary PrintWriter. Simply use the following code 
instead of calling XMLC.main() :

PrintWriter stdout = ...
PrintWriter stderr = ...
XMLC xmlc = new XMLC(stdout, stderr);
try {
  xmlc.compile(args);
} catch (Exception e) {
  // Handle errors here
}

If you want fine-grained control over the error handling, you can call the 
individual stages of XMLC (Parse, EditDOM, ClassGenerator, Javac) directly 
and process the errors through an special-purpose implementation of 
org.enhydra.xml.io.ErrorReporter. Have a look at the sources to find out the 
details - a good starting point is 
org.enhydra.xml.xmlc.commands.xmlc.XMLC.compile()

Hope this helps,

Richard

-- 
Richard Kunze 

[ t]ivano Software, Bahnhofstr. 18, 63263 Neu-Isenburg
Tel.: +49 6102 80 99 07 - 0, Fax.: +49 6102 80 99 07 - 1
http://www.tivano.de, kunze@xxxxxxxxx