I am glad to see the eclipse plug-in for XMLC. Would you consider
developing it using 2.2 instead of 2.1?
I would consider it, certainly. Is there a list of differences?
The compiling error of XMLC (and runtime errors) are directed to an
XMLCLogger. The default implementation of this interface is to used to
stderr. The Logger's API has been changed a bit between 2.1 and 2.2.
The stream used by the logger is no longer exposed so Log4J or logging
in JDK 1.4 can be plug in.
Thanks.
David Li
On Wednesday, Jan 15, 2003, at 00:14 Asia/Shanghai,
<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? Is this a byproduct of using many
different
parsers? Correct reporting of errors in Eclipse is going to be hard
if it
continues this way.
David Corbin
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
| 