Hi, In general I like the suggestion, but issues are hard to debug in case a servlet leverages the new feature but the servlet resolver doesn‘t support it. Can’t we work with Require/Provide Capability for that? Konrad
> Am 03.12.2019 um 15:54 schrieb Bertrand Delacretaz <[email protected]>: > > Hi, > > For SLING-8110 I'd like to take into account the > sling.servlet.extensions and sling.servlet.methods properties, if > present, on servlets that are mounted using the sling.servlet.paths > property. > > However that's not backwards compatible, as currently these properties > are silently ignored if sling.servlet.paths is present (*) > > To keep backwards compatibility, I suggest adding a new optional > sling.servlet.resolution property that for now can have the value > "strict". > > If that's present, the new SLING-8110 code takes into account the > sling.servlet.extensions and sling.servlet.methods properties, if > present, for a servlet that has a sling.servlet.paths property. > > If sling.servlet.resolution is not set, the resolution behaves as it does > today. > > WDYT? > > -Bertrand > > (*) As Konrad notes at SLING-8110 the latest annotations make it > harder to have such ignored properties, but technically nothing > prevents them from being present
