Re: What's the more convenient way to add logging to a tapestry app?

Hello: Finally I can do it using a Tomcat approach to configure the Logger (with context) that is instanciated by hivemind and now works the logging into pages. Thanks a lot Peter and Kevin for your help and time. JQ Peter Dawn escribió: i use log4J. try using that. --

Re: What's the more convenient way to add logging to a tapestry app?

Thanks for your responses, but I still has the problem to put the parameters into the ASO. I tried putting that into web.xml but the examples to read the InitParams involve init() procedure and the argument is the ServletContext. so I don't know how to access it if Tapestry wrap it and the init

Re: What's the more convenient way to add logging to a tapestry app?

i use log4J. try using that. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: What's the more convenient way to add logging to a tapestry app?

Thanks Kevin is that I want to see, only two more things 1) Now I have this error message: Unable to construct service com.pct.AjaxSIG.loggerContextFactory: Unable to convert type 'com.pct.commons.Helper.LoggerFactory' to a Java class, either as is, or in package com.pct.AjaxSIG My hivemodu

Re: What's the more convenient way to add logging to a tapestry app?

Jorge Quiroga wrote: Then I have to write a service after all, so do you know which interface I have to use (or define) to put in the invoke factory and service tags? See http://mail-archives.apache.org/mod_mbox/incubator-cayenne-user/200606.mbox/[EMAIL PROTECTED] It's an example of somethi

Re: What's the more convenient way to add logging to a tapestry app?

Jorge Quiroga wrote: Then I have to write a service after all, so do you know which interface I have to use (or define) to put in the invoke factory and service tags? org.apache.tapestry.engine.state.StateObjectFactory Despite being a service, it's nothing your code will ever use. It's going

Re: What's the more convenient way to add logging to a tapestry app?

Then I have to write a service after all, so do you know which interface I have to use (or define) to put in the invoke factory and service tags? Kevin Menard escribió: Jorge Quiroga wrote: I has a doubt about the create-instance part because commons-logging has its own LogFactory, and other

Re: What's the more convenient way to add logging to a tapestry app?

Jorge Quiroga wrote: I has a doubt about the create-instance part because commons-logging has its own LogFactory, and other doubt is about how I can set the properties file maybe (follow the example) class="org.apache.commons.logging.Log, log4j.configuration=/WEB-INF/classes/log4jproperties.x

Re: What's the more convenient way to add logging to a tapestry app?

Hello Kevin: Thanks Kevin, so, now I put on my hivemodule file this I has a doubt about the create-instance part because commons-logging has its own LogFactory, and other doubt is about how I can set the properties file maybe (follow the example) class="org.apache.common

Re: What's the more convenient way to add logging to a tapestry app?

Hi Jorge, It seems to me that an ASO would be your best bet. Give it an application scope and you'll only create a single instance for the life of your app. If you need to do some funky configuration when starting, then you can create a StateObjectFactory wrapper. A service would really on

What's the more convenient way to add logging to a tapestry app?

Hello Tap gurus: I was searching about logging into webapps, but I'm now overhelming and confused about how I can implement a real well done logging for tapestry apps, here I found some answers (some use services others instanciate the Logger inside a page that after inherit this feature, som

What's the more convenient way to add logging to a tapestry app?

Hello Tap gurus: I was searching about logging into webapps, but I'm now overhelming and confused about how I can implement a real well done logging for tapestry apps, here I found some answers (some use services others instanciate the Logger inside a page that after inherit this feature, som