Implement support for legacy class transitions in getSubcontext(String)
Basics
Logistics
Basics
Logistics
Description
Obnoxious, but I think we have little choice but to implement deprecation support to the string-based BaseContext.getSubcontext methods to allow classes to change. I hate these methods, but they’re the only reasonable way to allow navigation in Velocity and they’re used a lot in scripts too, so if we’re going to need to occasionally adjust classes, we have to accommodate it better than “sorry, it will break”.
It’s very much an IdP issue infecting OpenSAML but that’s where we put the contexts so not much choice.
Environment
None
Activity
Scott Cantor
June 1, 2023 at 9:17 PM
This is implemented so as to only execute on a ClassNotFoundException so it's not much overhead relative to what was already done.
Obnoxious, but I think we have little choice but to implement deprecation support to the string-based BaseContext.getSubcontext methods to allow classes to change. I hate these methods, but they’re the only reasonable way to allow navigation in Velocity and they’re used a lot in scripts too, so if we’re going to need to occasionally adjust classes, we have to accommodate it better than “sorry, it will break”.
It’s very much an IdP issue infecting OpenSAML but that’s where we put the contexts so not much choice.