>From looking a bit at the Muse source code, it seems that you would need to modify the Muse libraries.
In muse-core, under org.apache.muse.core.descriptor.LoggingConfig you would need to modify newInstance() to add whatever handler you want. david.brossard wrote: > > Hi, > > I'd like to customize the way a Muse web service is logging information. > I found the following so far: > > - Muse uses the JDK logging API > quote (from > http://ws.apache.org/muse/docs/2.2.0/manual/architecture/deployment-desc > riptor.html): > ________________________________ > Logging is done with the JDK logging API. The two elements under > <logging/> - <log-file/> and <log-level/> - allow you to specify where > the Muse log file will be written and at what level of detail it should > record, respectively. > > The log file path should be relative to the application's > working directory; in the case of the J2EE, this is the root of the WAR. > The sample project will create a log file at > /WEB-INF/services/muse/log/muse.log. The file will be overwritten each > time the application is restarted. > ________________________________ > > > - Java Logging can be extended with new handlers > quote (from > http://java.sun.com/j2se/1.5.0/docs/guide/logging/overview.html#1.5): > ________________________________ > J2SE provides the following Handlers: > > * StreamHandler: A simple handler for writing formatted records > to an OutputStream. > * ConsoleHandler: A simple handler for writing formatted records > to System.err > * FileHandler: A handler that writes formatted log records > either to a single file, or to a set of rotating log files. > * SocketHandler: A handler that writes formatted log records to > remote TCP ports. > * MemoryHandler: A handler that buffers log records in memory. > > It is fairly straightforward to develop new Handlers. Developers > requiring specific functionality can either develop a Handler from > scratch or subclass one of the provided Handlers. > ________________________________ > > > Obviously one needs to write a configuration file: > quote(from > http://java.sun.com/j2se/1.5.0/docs/guide/logging/overview.html#1.8): > ________________________________ > The logging configuration can be initialized using a logging > configuration file that will be read at startup. This logging > configuration file is in standard java.util.Properties format. > ________________________________ > > But my understanding is that the muse framework programmatically > configures the logging framework based on the values read from the > muse.xml which are a file name and logging level which hints at saying > there is only one possible logging destination: a file. In that case, > there is no way one can use a custom handler, is there? Let alone use a > pre-existing one. > > Does anyone have an idea? What would be the behavior if I did put in a > java logging config file? I suppose that the assumed programatic > configuration would take precedence on the one from the file effectively > cancelling out the latter's effect. > > Thanks, David. > > > David Brossard > Security Research Professional > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Capability-URIs-and-Resource-Property-Namespaces-tf4349601.html#a12394933 Sent from the Muse User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
