incompatible change to PolicyContext.getHandlerKeys about authorization HOT 4 CLOSED

@bshannon Okay, I'll revert it and then re-stage the artefact. Thanks for testing this!

P.s. I think similar changes were made for Servlet were @markt-asf mentioned it was technically a compatible change from a JLS point of view.

from authorization.

The generics are erased at compile time so the run-time impact of this change should be zero. Depending on where in the API the generics are added and how the API is used there may be compile time impacts (i.e. users would need to modify their code to compile against the version with the generics).
It is a judgement call whether that impact is acceptable or not.
I checked the servlet-api project. No generics changes were made. I think that was addressed back in JavaEE 6 for Servlet (servlet 3.0).

from authorization.

Whether this would cause any incompatibility to applications is not the issue.
This is a change from what the specification required and thus must be fixed.
If you believe there is no impact to applications, you can consider this change
in a future version of the specification.

from authorization.

@bshannon I understand. For JACC (and JASPIC among others) I'll propose changes such as this for the next spec rev.

The change has been reverted as requested, and the artefact has been restaged again.

See

• https://jenkins.eclipse.org/jacc/job/jacc-release-build/18/consoleText
• https://oss.sonatype.org/content/repositories/staging/jakarta/security/jacc/jakarta.security.jacc-api/1.6.1/

I think this closes the issue then. If there's anything else please let me know.

from authorization.