/
Migration of policy xacml-pdp to Java 17

Migration of policy xacml-pdp to Java 17

As already defined, the main blocker for policy/xacml-pdp is the com.att.research:xacml-pdp dependency (AT&T's reference implementation of the OASIS XACML 3.0 Standard.)

<dependency> <groupId>com.att.research.xacml</groupId> <artifactId>xacml-pdp</artifactId> <version>3.1.0</version> </dependency>

The com.att.research:xacml-pdp dependency uses javax XML binding non compatible with java 17. (Last xacml-pdp release could be found here: https://mvnrepository.com/artifact/com.att.research.xacml/xacml-pdp/3.1.0)

Information about Jakarta could found here: https://en.wikipedia.org/wiki/Jakarta_EE

The Jakarta EE 9 release on Dec 8th, 2020, would introduce jakarta.* as the namespace to replace javax.* for Jakarta EE specifications. (Full article is here: https://jakarta.ee/blogs/javax-jakartaee-namespace-ecosystem-progress/)

Last Jakarta release, Jakarta EE 10 as minimum Java SE Version, Java SE 11 or higher.

Valid options for com.att.research:xacml-pdp and .att.research:xacml to move as major version:

  • only migrate to Jakarta EE 10 and maintain the compatibility with Java 11


  • migrate to Jakarta EE 10 and Java 17 (maybe the best option)







Related content

Dependency Upgrade in Policy Framework
Dependency Upgrade in Policy Framework
More like this
Policy R10 Jakarta Release Planning
Policy R10 Jakarta Release Planning
More like this
Honolulu Exception Request for AAI
Honolulu Exception Request for AAI
More like this
2025-02-04 Security Subcommittee Meeting Notes
2025-02-04 Security Subcommittee Meeting Notes
More like this
Jakarta Release Requirements
Jakarta Release Requirements
More like this
Policy R6 Frankfurt M1 Release Planning Template
Policy R6 Frankfurt M1 Release Planning Template
More like this