Curt Arnold <carnold <at> apache.org> writes:
> The exception occurs since you specified that you wanted to use the > classes "javax.faces" and "org.apache.myfaces" as implementations of > the org.apache.log4j.Category contract. As previously noted, the > term "logger" has replaced "category" long time ago (but "category" > is still there for compatibility). Since you did not implement > classes named "javax.faces" or "org.apache.myfaces" that extended > "org.apache.log4j.Category", you were bound to get an exception. > > You appear like you may be hoping that log4j can magically add > logging code to an implementation classes in "org.apache.myfaces" or > "javax.faces" packages. Log4j and other common logging frameworks > require explicitly coding logging requests within a body of code and > the authors of the code choose their own naming convention. The type > of behavior that you may be looking for would require an aspect > oriented language like AspectJ. > I was under the impression that name="org.apache.myfaces" property of <logger> for example would be the way the logger knew to only log debug/info from everything containing that package name. <P> If I name it anything I want, like name="idMyfaces" how does the logger limit output confined to "org.apache.myfaces.*" ? <P> Is there something I am missing? <P> Lisa --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
