Skip to content

Commit 40ddfef

Browse files
committed
Update JAX-RS compatibility in README
1 parent 9ccbee9 commit 40ddfef

File tree

1 file changed

+8
-8
lines changed

1 file changed

+8
-8
lines changed

README.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -603,14 +603,14 @@ Conjur conjur = new Conjur();
603603
String secret = conjur.variables().retrieveSecret("<VARIABLE_ID>");
604604
```
605605

606-
## JAX-RS Implementations
607-
608-
The Conjur API client uses the JAX-RS standard to make requests to the Conjur web services.
609-
In the future we plan to remove this dependency, but for the time being you may need to
610-
change the JAX-RS implementation to conform to your environment and application dependencies.
611-
Conjur API uses Apache CXF by default but for example, in a JBoss server environment, you
612-
should use the RESTlet implementation. You can replace that dependency in `pom.xml` to use an
613-
alternative implementation.
606+
## Jakarta REST (JAX-RS) Implementations
607+
The Conjur API client uses the Jakarta REST (formerly JAX-RS) standard to make requests to the Conjur web services.
608+
It is compatible with Jakarta EE environments and may not work in Java EE environments that still use the
609+
older javax.ws.rs packages.
610+
611+
Conjur API uses Jersey as the default Jakarta REST implementation for client requests. While it is broadly compatible,
612+
some application servers (e.g., JBoss EAP or WildFly) may require overriding the Jersey dependency in `pom.xml` to
613+
avoid conflicts.
614614

615615
## Troubleshooting
616616

0 commit comments

Comments
 (0)