Piers,
IIRC, JBoss 6, by default, prefers the parent class loaders over child class
loaders. This means that, when a class path resource is referenced, it is first
searched for in the server class loaders and _then_ in the web application
class loader. This is similar to the default behavior in
Piers,
I've not done this on JBoss 6.
If your application uses Spring Framework, you could initialize log4j using
their org.springframework.web.util.Log4jConfigListener as described in this
blog [1].
If you aren't using Spring, you can still take a similar approach - create
a ServletContextListe
Piers,
To be honest, this sounds more like a question that should be directed to the
JBoss people...
Kind regards,
Remko
Sent from my iPhone
On 2013/05/20, at 22:45, Piers Uso Walter wrote:
> Hi,
>
> I am migrating an application from JBoss 4 to JBoss 6 and stumble over the
> fact that log
