log4j in EJB container
All,
Log4j uses static members to access and manage loggers. Given that the EJB specs explicitly tell us not to use non-final static members in the EJB container, is using log4j in EJBs problematic? I'm having a hard time coming up with a real-world exampel of where this would be a problem (although I would expect there would be some situations where class loader issues could cause a loss of state withing the logger manager).
A couple of of questions...
1. Is using log4j in the EJB container something I really need to be concerned about?
2. Other than non-final static data members - which are prohibited - is there a way I can cache and manage 'global' level data or implement a singleton in the EJB container?
3. Is there anything in the new EJB specs that address this whole issue?
