This content has been marked as final.
Show 4 replies
-
1. Re: Classloading behavior change in current Branch_4_0
starksm64 Nov 12, 2004 11:05 AM (in response to jason.greene)As documented in the release notes, the default config uses scoped class loading by default and so there is no visiblity into application deployments. The standard configuration is equivalent to the default configuration in 3.2.
-
2. Re: Classloading behavior change in current Branch_4_0
jason.greene Nov 12, 2004 11:14 AM (in response to jason.greene)Both of these are using the default scoping config. I am talking about the difference between 4.0.0 and the latest in the 4.0 cvs branch.
-
3. Re: Classloading behavior change in current Branch_4_0
jason.greene Nov 12, 2004 11:18 AM (in response to jason.greene)nevermind it turns out that the build for the branch has identical configs for server/default and server/standard.
-
4. Re: Classloading behavior change in current Branch_4_0
starksm64 Nov 12, 2004 11:19 AM (in response to jason.greene)The build of the 4.0 branch does not impose the scoped class loading in the default configuration. This is only done for releases, and will be undone for the 4.0.1 release since its causing so much grief.