Dmitry -
> "relying on the old behavior is relying on a bug"
I'm pretty certain that you already agreed that this application is doing something wrong. As I stated previously, this application is relying on a behavior that is not spec compliant. That is a bug and it doesn't matter how long it's been a bug for.
> Since what time we stopped caring about backwards compatibility?
Not once have I said that we don't care about compatibility. When making branch level changes, compatibility is paramount. On major release boundaries it is a slightly different story. I think a a release boundary we have the duty to fix bugs/behaviors in the correct manner for future customers yet give existing users the ability to revert to the old (and sometimes incorrect) behavior. You can't expect an application that is working on 2.3.0 to work in the exact same manner on 2.6.0. If that was the case we could never add new function, fix bugs, etc, etc.
> And now we changed them to achieve some questionable advantages.
I've made my case and if you feel that this functionality isn't the correct behavior for WLS, go ahead and disable the WebLogicPlatformDetector. I don't think that is the right answer, but do what you must.
Thanks,
Rick