Understanding Classloaders: log4j in a J2EE Environment
Subject:   How about utility.jar for multiple EARs?
Date:   2003-04-07 03:22:50
From:   anonymous2
If I have a common jar for multplie EARs, for example, I don't want everyone to pack his own version of log4j, what can i do?
Full Threads Newest First

Showing messages 1 through 1 of 1.

  • How about utility.jar for multiple EARs?
    2003-04-11 05:18:51  gvix [View]


    I am not sure if I understand you question.

    Based on what I think you are asking, I would suggest that if you have a jar that a host of other EAR's require, deploy it on the system classpath. The idea is, that if it a system wide utility library, a change in this library would have an effect system wide. It's almost equivalent to a change in Weblogic classes. Your server will need to be restarted and I think if it is system wide, you might as well put it on the Weblogic classpath.

    Vikram Goyal