It is ok if your initializing the category once per class as is all you need
for
a classname based category. Similarly an infrequent initialization step is
fine also.
If you start adding per instance or even worse per method based context then
logging starts being intrusive.
> >
>
> Are you sure that there is a lot of overhead when obtaining a logging
> category? If there is, I will make sure to obtain all categories during
> container initialization and not on the fly. I assume that it is ok to
> perform expensive operations during initialization.
>
> -dain
>
> > ----- Original Message -----
> > From: "Dain Sundstrom" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, July 11, 2001 7:46 AM
> > Subject: [JBoss-dev] RE: [JBoss-user] log4j or JBoss logging
> >
> >
> > > I posted the original message to the wrong forum (user
> > forum), and almost
> > > lost the responses in all the traffic.
> > >
> > > I will switch over to direct log4j soon.
> > >
> > > Has anyone given any thought to how we should organize the
> > log categories?
> > >
> > > For example, what root are we going to use 'jboss' or 'org.jboss'?
> > >
> > > I think we should follow class package name as close a
> > possible, so cmp
> > > messages would start at 'org.jboss.ejb.plugins.cmp'.
> > >
> > > My current plan is to use
> > > 'org.jboss.ejb.plugins.cmp.<BeanName>.<JDBCCommandName>'
> > >
> > > -dain
> > >
> >
> >
> >
> > _______________________________________________
> > Jboss-development mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/jboss-development
> >
>
> _______________________________________________
> Jboss-development mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/jboss-development
>
_______________________________________________
Jboss-development mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/jboss-development
