This content has been marked as final.
Show 2 replies
-
1. Re: Why are some security domains visible in JNDIView and ot
j2ee_junkie Aug 2, 2006 8:10 AM (in response to fhh)fhh,
I believe that the login-config.xml file is loaded by the server, but actual SecurityDomain/SecurityManagers are not instantiated and bound in JNDI until they are needed. An example of when one would be needed is when an application specifically says, "I am using security domain x" at deploy time.
cgriffith -
2. Re: Why are some security domains visible in JNDIView and ot
fhh Aug 2, 2006 3:59 PM (in response to fhh)Thanks fpr your reply!
I believe that the login-config.xml file is loaded by the server, but actual SecurityDomain/SecurityManagers are not instantiated and bound in JNDI until they are needed. An example of when one would be needed is when an application specifically says, "I am using security domain x" at deploy time.
That is what I would have expected but this is not the case. While poking around some more I have finally figured out that the security domain is not instantiated at deployment time but on first access.
Since some of the security domains are used internally they are visible in JNDI right after boot. Those that are configured but not used in the standard configuration are not visible until first use.
Regards
fhh