: 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
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
: 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
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
4 matches
Mail list logo
