Hi!
Oleg Nitz wrote:
> RO> Why?
> Because after the last cvs update I get "not serializable" exception
> on deployment :-)
> I guess, this is because JaasSecurityManager is bound to JNDI and
> something has been changed in JNP.
On second thought, no I don't understand what you're doing with JNDI.
First you are binding the JSMS to "jaas" and then you are creating a new
subcontext "jaas.sm" parallel to "jaas" in the root context (i.e. in the
root of JNDI you will have a "jaas" binding and a subcontext called
"jaas.sm". Why do you have a "." in the name BTW?) , and then on lookup
you bind new JSM's into the "jaas.sm" subcontext. Why? First of all, can
there be many JSM's? And should they really be created on the fly as you
do now if they're not already created when the lookup is done? And why
don't you simply use a hashtable where you store the JSM's instead of
the "jaas.sm" subcontext?
Can you please explain what you want to do with this code.
regards,
Rickard
--
Rickard �berg
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
