Re: Nuke XInvoke & XSyslog?
Peter Donald <peter-4lf8KW9E9MLMqX/[email protected]> Sat, 6 Dec 2003 15:41:07 +1100
| Newsgroups | gmane.comp.java.spice.devel |
|---|---|
| Message-ID | <[email protected]> |
On Fri, 5 Dec 2003 07:57 pm, Johan Sj=F6berg wrote: > Peter Donald wrote: > > Hiya, > > > > I was contemplating nuking xsyslog and xinvoke from the sanbox. xinvo= ke > > was a basic interceptor api that just never got finished and probably > > wont anytime soon. Xsyslog was a configuration mechanism for loggers = but > > also never got finished. > > How did Xsyslog work? Essentially all id did was read in an xml configuration file, build a met= adata=20 representation of configuration, validate the configuration and then crea= te a=20 set of Loggers for specified metadata. It was kind of like an enhanced=20 Excalibur-Logger that could target multiple output Loggers (ie could=20 configure JDK Logging or LogKit depending on provider) and it was much=20 "safer" (ie xml schemas would be used to validate configuration and the=20 metadata validated the inter-logger setup etc. However it is not finished so not so useful. --=20 Cheers, Peter Donald *---------------------------------------------* | "The only way to discover the limits of the | | possible is to go beyond them into the | | impossible." -Arthur C. Clarke | *---------------------------------------------*