Out of curiosity: why would you want the component logger?
If you create one locally (private static final Logger log = LoggerFactory.getLogger(YourClass.class);), you have the benefit of controlling log output since the logger is bound to the actual component and not the superclass. E.g. at runtime you can change a certain page or component (or other class) to display more or less verbose logging.
Op 14-10-2011 14:47, schreef hok:
Hello, the Component and WebPage classes have a private property /log/. Sometimes in Pages and Components there is a need for logging, but in this case the user have to instantiate separate logger, since the existing is not accessible. Do you think it's possible to make the logger protected, or provide a getter? Thanks. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/private-Logger-log-property-in-WebPage-and-Component-tp3904720p3904720.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
