Classloading behavior change in current Branch_4_0

[jason.greene]

I currently have a custom JAAS module inside a sar that is within an ear file. I noticed a problem with this setup in 4.0.0, when attempting to use the same security module for web authentication in an external war. If I for example, go to the jmx-console and invoke isValid() on the JassSecurityManager, a classloading exception occurs complaining about not being able to find the login module class that is in the nested sar.

However, in the current Branch_4_0, the classloader successfully finds and loads the class in the sar that is nested in an ear file.

What should the correct behavior be? Should the JaasSecurityManager called from an external war be able to find classes in a sar that is nested within an ear?

[starksm64]

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.

[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.

[jason.greene]

nevermind it turns out that the build for the branch has identical configs for server/default and server/standard.

[starksm64]

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.