[Wonder-disc] ERXLocalizer enhancement

[<anj...@t-...>]

All,

As stated in the CVS commit, I put the session's localizer in the per-thread
storage which will decouple from the session object. I also fixed
ERXValidationFactory to choose the language accordingly, eliminating the
need to set the language explicitly.

In plain language: you don't need to have special handling anymore between
ERXValidation messages and NSValidation messages, because
ERXValidationException.getMessage() will know to resolve correctly.

This in fact makes the languages() setting in ERXValidationException
obsolete...I wonder if one should keep it around for more flexibility?

For your own code: use

ERXLocalizer.currentLocalizer()

to get the currently active localizer of the thread.

And yes, I *do* plan to comment the class in the near future :)

Cheers, Anjo

PS: In case someone is an Apple Developer member that doesn't need one of
his hardware rebate keys, I'd like to buy an iBook in the near future and
have already gave my key to a friend...I'd really appreciate it if someone
would be so kind as to offer one of his:)