-
1. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
starksm64 May 5, 2005 8:43 PM (in response to javaspack)There should never be a j2ee.jar in the war in any app server. This has to be provided by the app server. Read the release notes for the class loading config change.
-
2. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
grafpoo May 9, 2005 11:45 AM (in response to javaspack)i've had the same error message about the appender, but it came about because i have log4j1.2.8.jar in my war file. when i remove it from the war file, all is well.
but i don't want to remove it from the war-file; i want to try to keep my war deploy app-server-agnostic.
i've just looked at the release notes, which point me to JBAS-1691, which says i can restore old behavior by setting a couple of attributes (Java2ClassLoadingCompliance and UseJBossWebLoader), but i'd prefer having an out-of-the-box jboss work with my war (with log4j).
willing to admit i've fudged this ... john -
3. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
grafpoo May 9, 2005 11:46 AM (in response to javaspack)by the way, i am running java 1.5_03...
-
4. Re: JBoss 4.0.1sp1 to 4.0.2 upgrade problem
starksm64 May 9, 2005 12:47 PM (in response to javaspack)When a deployment includes classes used by the implementation of the app server, you don't have an app server agnostic deployment by definition. Either the class loading configuration of the app server needs to be configured to work with your packaging, or the packaging updated to work with the default app server configuration.