Hi all,
First of all: My name is Carlos and I'm new here. (I have entered the list a few days ago) And I'm still trying to understand the tomcat source code... oh... and I'm not from USA...my english is not perfect, but I hope I can be usefull anyway.... ;)
I was looking for something to work on, and I found this in BugZilla: http:// issues.apache.org/bugzilla/show_bug.cgi?id=25953
I know this is a minor enhancement but I think It's a good place for me to start. Before start coding (or even thinking about it) I would like to know if anyone already did it!
Thinking about the issue, I couldn't figure out how to do it without changing the signature of the authenticate() method (which is the worst choice, I think) or creating a new method that can throw some kind of exception to be catched by the user application (maybe deprecating the authenticate() ??). Do you have any ideas?
Not really ;)
This may not be the best bug to start with, although it does sound simple. The problems are:
- likely there will be an API change needed
- not all realms may support every error messages, and all will need different impls
- if most realms don't support it, then the feature is useless, so isn't worth the pain of the API change mentioned above
So to sumarize, I think you should pick another bug :)
So ideas:
- lurk in the TC 4 bugs like Mark is doing to see if anything still applies to TC 5
- work on the admin webapp (some patches pending - testing needed ! - and a few bugs open)
- 26236 about the JAAS realm: it would be a very useful fix, and shouldn't be too complex
Rémy
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
