If there is a "log" property on your service implementation, then HiveMind will automatically bind it with a Log object with the name of the service point's id. So, the ComponentConstructorFactoryImpl object gets a Log for "tapestry.enhance.ComponentConstructorFactory" since that's its service point id. For more information on how HiveMind "autowires" stuff:
http://jakarta.apache.org/hivemind/hivemind/BuilderFactory.html#Autowiring Note: the documentation will be moving soon once we get the HiveMind TLP move completed. -----Original Message----- From: Karthik N [mailto:[EMAIL PROTECTED] Sent: Friday, October 13, 2006 8:29 AM To: Tapestry users Subject: Re: Tap 4.0.2: How to enable Logging to log enhanced class source code?? Kind of answering my own question: log4j.logger.tapestry.enhance=DEBUG does the trick. I can see the enhanced source code being printed. The unanswered part for me, but more for academic interest is: How the log4j configuration translates to hivemind knowing to create a new Log object for the ComponentConstructorFactoryImpl is something I've not been able to figure yet!! --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
