If you use <hidden-classes> or <import-package>, you *must have* another log4j.jar in the sharedlib or your application itself. Because hidden-class will block to load the log4j.jar of the server. So if you don't have another log4j.jar copy, the jdk couldn't find any log4j implementation. It will fail to output your log.
2012/10/16 jcyim <jongch...@gmail.com> > thank you for your kind replies. > > I mean I did use <hidden-classes> and <import-package>, but it didn't work. > ( surely, I copyed log4j.jar into shared lib) > > Anyway, Even though I use <hiddend-classes> and <import-package> in order > to > do not load geronimos's native logging libraries. > I think Geronimo's pax logging classes are still loaded. > The only way I was successful was to put log4.jar library into my app's > lib. > > I doubt that Geronimo's native logging class can not be hidden in Geronimo > 3.0. > > Surely, I can use the way you suggested, but a little concern is that's not > self contained. > However that's not a big deal. I can use it. > > > > > -- > View this message in context: > http://apache-geronimo.328035.n3.nabble.com/geronimo-3-0-application-specific-logging-tp3985902p3985914.html > Sent from the Users mailing list archive at Nabble.com. > -- Best Regards Gary
