Hi Alex, In RC1 we indeed removed the per-application access log in favor of a shared access log attached to the Component. This service only logs server-side accesses to the component (via server connectors) and writes them in an Apache-like format. The logger name used for this purpose it something like "org.restlet.Component" by default.
Now, there is another type of logging used for code debugging (info, warnings, traces, etc.), based on the calls to "getContext.getLogger()". Are you referring to this type of logging? For this one, the logger name used by applications is "org.restlet.Application" by default and can be changed using Context.setLogger(). As the default will be the same for all applications, I have just changed it to the canonical class name of the application (i.e. the qualified Application subclass name). If the application is an anonymous class, it doesn't have a canonical name and "org.restlet.application" will be used. Committed to SVN. Let me know if I have misunderstood your problem. Also, the error in the tutorial has been fixed in SVN and the update will appear online soon. Thanks for reporting it! Best regards, Jerome > -----Message d'origine----- > De : news [mailto:[EMAIL PROTECTED] De la part de Alex Combs > Envoyé : mercredi 21 février 2007 20:24 > À : discuss@restlet.tigris.org > Objet : possible Application Access Logging bug > > Run into a bit of an issue: It seems that if I create an > Application and attach > it to a Component, the Application no longer makes use of the > Component's access > logger. I'm guessing this dates back to RC1 and the deprecation of > Application's logService, but if this is the case, how do I > go about re-enabling > Access Logging for my Application? It's already nicely defined for my > Component's logService, I just need a way to get Application > to use it too. > > On a related note: The Tutorial's Section 7 should probably > be updated, since > you can't modify an Application's logService property anymore.
