This feels a bit like an over-statement, we probably use servlet specific apis in less than 10% of our modules, probably more like 1-5%. 0% in commons, probably 0% in rendering too and a bit more in platform, maybe 10%.
In this case the solution is 2. Right now we’re missing a scripting service for container because we didn’t see the need or forgot to add it, but it’s logical to have one if we keep the concept of container.
And no direct injection in java, instead get whatever is needed from the container api.
But I understood from this thread and the other one at Introduce new jakarta servlet related APIs that we were questioning the need for the container api. And it’s not new. So maybe it’s the time to decide what we do about it since it impacts the decision on new apis, including this thread.