Hi, Jules,
I've used the following hack, which, in fact worked. In JBossUserPrincipal, where you set SecurityAssociation, instead of setting the principal to 'this', set it to 'new SimplePrincipal(this.getName())'. JBoss security checking will not care if it is a new object every time. Another question. I am having trouble with env being not bound with the new Jetty from CVS. (Meaning, when a WAR gets deployed, it does not see ejb-ref if the JNDI name is in the comp/env space.) I used to have this problem some time before but syncing with the latest JBoss CVS fixed it. Would you happen to know why this happens? I really need to get this to work... Anatoly. On Wed, 2 Jan 2002, Jules Gosnell wrote: > For the moment, I am not implementing the Security integration between Jetty > and JBoss as Serializable. > > I understand why you feel it should be a requirement for the future, and > agree with you. Unfortunately, it is not simply a case of shipping a string > since the same Principal object has to be useful within Jetty, which expects > it to have behaviour based on state which is not so easily serializable. > > Provided that the completion of the ClassLoader work will resolve the > immediate issue of the testsuite failing here I shall put it on my todo list > and tackle it next time I revisit the security integration. > > If anyone feels there is good reason for this to be prioritised more highly, > please let me know. > > _______________________________________________ Jboss-development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
