|
Re: Logging from within EJBs: msg#00272java.jboss.user
> How can JBoss deprecate an interface in a separate package? Category has been deprecated by the log4j project: "This class has been deprecated and replaced by the Logger subclass. It will be kept around to preserve backward compatibility until mid 2003. Logger is a subclass of Category, i.e. it extends Category. In other words, a logger is a category. Thus, all operations that can be performed on a category can be performed on a logger. Whenever log4j is asked to produce a Category object, it will instead produce a Logger object. However, methods that previously accepted category objects still continue to accept category objects. For example, the following are all legal and will work as expected. // Deprecated form: Category cat = Category.getInstance("foo.bar") // Preferred form for retrieving loggers: Logger logger = Logger.getLogger("foo.bar") The first form is deprecated and should be avoided. There is absolutely no need for new client code to use or refer to the Category class. Whenever possible, please avoid referring to it or using it." http://jakarta.apache.org/log4j/docs/api/index.html Andreas ------------------------------------------------------- This sf.net email is sponsored by:ThinkGeek Oh, it's good to be a geek. http://thinkgeek.com/sf
|
|
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| Previous by Date: | Re: Logging from within EJBs, Guy Rouillier |
|---|---|
| Next by Date: | Re: Logging from within EJBs, Guy Rouillier |
| Previous by Thread: | Re: Logging from within EJBs, Guy Rouillier |
| Next by Thread: | Re: Logging from within EJBs, Guy Rouillier |
| Indexes: | [Date] [Thread] [Top] [All Lists] |
| News | FAQ | advertise |