I was referring to the backwards compatability issues raised by Niall. He
raises the concern that someone may be storing an action definition in the
request using the ACTION_DEFINITION key. If so, the patch related to the
RequestProcessor will cause this mechanism to fail.
It seems to me that not many people are doing this, and the key's primary
purpose is no longer necessary (even though technically it could be considered
a backwards compatability problem.)
My point is that the key itself is deprecated and part of a deprecated class.
This is what I mean by "its going away soon" (not the request processor.) So
if someone is using this key in a current application, they are getting
deprecation warnings. In my mind, it would not be unfair to remove this key
(and all references to the deprecated DefinitionsUtil class) in the next
You can't remove DefinitionsUtil until you make these fixes I'm suggesting.
Once these fixes are made, then I believe we could nix the DefinitionsUtil
class. Dropping DefintionsUtil can be done now or later depending on the
groups policies towards deprecation and how long is appropriate.
If we're not going to make the patches now, I recommend creating a new bug
entry for dropping DefinitionsUtil and making it dependent on this bug entry.
Then both can be done at the same time.