>> One fairly simple way to integrate Log4J would be to write an
>> implementation of org.apache.catalina.Logger that uses it. This will
>> undoubtedly not suffice for a final solution, because it does not expose
>> all of the logging flexibility that Log4J provides. But it might serve as
>> a starting point for experimentation (and learning how we might deal with
>> the hierarchy as well as configuration from bean properties so that
>> server.xml parsing does it for you automatically).
>
>
> My current impression is that this can be counter productive. It will probably
>require less effort to move to log4j in one step (assuming the step is well planned)
>than trying to retrofit log4j to the existing logger. My intention was to prepare a
>solid migration plan and follow it through.
>
> Come to think of it, the retrofitting solution would not be difficult but the result
>will probably not be very convincing.
>
>
Since I had so shamelessly copied Craig's Services model out of Catalina
to use it in another project that never made it, I actually have some
experience with this. I had really appreciated the logging in the
Catalina framework, because it was always there, and it was configurable
per component. My cohort converted the whole thing to use Log4J in two
days, and I was even happier after that. We had started with the
retrofitting solution, but it was easier in the end to define a standard
way to get the Category, and then cut and paste that code everywhere we
needed it. So, I would say go for the whole hog, as it is not very hard
;-)
I'd even offer to help ;-)
>>
>> Categories are your friend.
+1!
Scott Sanders
