The same changes were done in Tomcat due to the new Servlet 3.0 authenticate(HttpServletResponse response) in javax,servlet.http
At first glance I didn't think that your suggested change of adding back the "register" with the Request parameter would help. After all, if you have a Request object you can already pass it to the HttpServletResponse version.
However I was wrong. Your suggestions maintains run-time compatibility, so that code compiled under the old signature will run with the new version.
I made an additional suggestion here: https://community.jboss.org/message/547145#547145
Nick and Jean-Frederic,
Thanks for the responses. My intent was to make sure JBoss was aware of the problem with backward compatibility. Especially before the official JBoss 6 version is released. I ran into the problem while trying to verify that my company software still worked with the new JBoss 6 release.
Moving forward, I have already implemented a working solution. It required using reflection and is kind of ugly. But I have spent plenty of time with this and currently that seems to be the only 'good' solution from my side (without having the original signature). Since I have no control over what JBoss decides to do, I had to move forward with the assumption that nothing would happen.
I would hope that asking for both method signatures in the AuthenticatorBase class is not an unreasable request. Maybe this isn't the right place to ask for the request? If I knew who to talk to about it I would.