|
I'll dig into this deeper and come back with a proposal. Aaron Mulder wrote: In order to do this right, I think we should define an interface for web server request log access. That interface should have a method that searches the logs, like the server log GBean does, so rather than the console code asking the web server for log files and then opening files and scanning them, the console should pass a bunch of search parameters to the web server, and the web server should identify and search its own logs and just return the results to the console. If the web server has multiple logs, I guess it should have a method that gets a list of log file names, so the portlet can let you select the log to query, and the search method can take the log file name as a parameter. -- Joe Bohn [EMAIL PROTECTED] "He is no fool who gives what he cannot keep, to gain what he cannot lose." -- Jim Elliot |
- Re: Tomcat, logging, admin portlet, and GBeans Joe Bohn
- Re: Tomcat, logging, admin portlet, and GBeans Joe Bohn
- Re: Tomcat, logging, admin portlet, and GBeans Joe Bohn
- Re: Tomcat, logging, admin portlet, and GBeans David Jencks
- Re: Tomcat, logging, admin portlet, and GBeans Aaron Mulder
- Re: Tomcat, logging, admin portlet, and GBeans Joe Bohn
- Re: Tomcat, logging, admin portlet, and GBe... David Jencks
- Re: Tomcat, logging, admin portlet, an... Aaron Mulder
- Re: Tomcat, logging, admin portlet... Bill Stoddard
- Re: Tomcat, logging, admin por... David Jencks
- Re: Tomcat, logging, admin por... Joe Bohn
