Hi Alex, That's correct, the Component.getLogService() method creates a default service if none was already set. I have just updated the Javadocs of the method with this:
/** * Returns the global log service. On the first call, if no log service was * defined via the [EMAIL PROTECTED] #setLogService(LogService)} method, then a default * logger service is created. This default service is enabled by default and * has a logger name composed of the canonical name of the current * component's class or subclass, appended with the instance hash code * between parenthesis (eg. "com.mycompany.MyComponent(1439)"). * * @return The global log service. */ Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Alex Combs > Envoyé : jeudi 22 février 2007 19:51 > À : discuss@restlet.tigris.org > Objet : Re: possible Application Access Logging bug > > Hmm, well I've found the reason. It was basically an > artifact from the b20->rc4 > migration. I was creating a new LogService with the desired > names and doing > component.setLogService(myLogService), but apparently the > default log service > had some special set up that the new one didn't that allowed > calls to be sent to > the accesslog. > > If you want to set it up that way, that's fine, I just think that the > documentation should give some warning to people who think, > like I did, that > they could just swap out the LogService object at will. >