0 Replies Latest reply on Jul 26, 2005 3:10 PM by Venkat Jagadeesan

    ZERO JBoss Dependency J2EE 1.4 compliant WAR deployment

    Venkat Jagadeesan Newbie

      Dear Jboss gurus,

      I have been rummaging through the documentation, the forums and the world-wide web for a clear answer to the following problem and have come up empty-handed. One of the threads "Log4j - separating logging from jBoss logging" had repeated mentioning of this from its originator "bmelloni" but it subsequently digressed into getting just log4j to work. So without further ado I am going to attempt to articulate the problem and see if I can get some pertinent responses -

      With JBoss 3.2.6 and JBoss 4.0.1SP1 (if it is different), what would be the configuration settings and/or deployment descriptors necessary to ensure that a deployed WAR is fully self-contained ? In other words how can I ensure that this WAR can

      a) be deployed as-is (other than inclusions of vendor-specific deployment descriptors) into another J2EE 1.4 compliant container and expected to run as in JBoss, in keeping with the "write-once, run anywhere" paradigm.

      b) contain any dependent libraries or jars that can be freely upgraded (or retrograded for that matter) as and when desired by the developer/deployer.

      c) contain library specific configuration and/or resource files (e.g log4j.xml/log4j.properties and/or commons-logging.properties) that will be honored by the container.

      From the Wiki and other documentation pages, it seems as though The Java2ClassLoadingCompliance and UseJBossWebLoader flags also have a significant impact on how deployments are isolated and I am interested in an understanding of how (if at all) these can aid in the objectives above, again independently for Jboss 3.2.6 and JBoss 4.0.1SP1, if they are infact different for the 2 versions.

      Thanks very much in anticipation..

      VJ --