Ate Douma wrote:
<snip>
2) Try to convince the Tomcat crew to revert to the old Tomcat 4 behavior. Maybe conditionally with an additional realm parameter? I have a gut feeling they are not open to this but maybe Jetspeed is important enough to make a difference???
Well there is an obvious issue: You have one behavior in Tomcat 4, and another behavior in Tomcat 5 One would think the Tomcat team would want to minimize these kind of issues. I think we should try to make an argument
This sounds like the solution for now, until we can sort out #23) Create an extended JAASRealm implementation or patch the current one without the new Tomcat 5 ContextClassLoader problems. This would be a short and simple solution (I tried it out: 5 minutes work) but it creates a dependency on the current Tomcat 5 implementation and requires putting the hacked/extended class in the server classpath.
That's +3 (including mine) for option #3. If nobody is going to object I will create a new issue and a patch this evening for this solution.
I'm also +1 for option #2: sorting it out with the Tomcat Team. But even if they are willing to revert back to the Tomcat 4 behaviour, I expect it will take to long to have no solution for now. Solution #3 will cover that.
Sounds like a good strategy. Having solution #3 in place until the Tomcat team might implement Tomcat 4 behavior in Tomcat 5. This allows us to continue with the J2 development for tomcat 4 and 5.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
