interestingly, if you do not specify rs-api,
jersey-container-servlet:jar:3.1.8 pulls in ws.rs-api:jar:3.1.0
[INFO] +-
org.glassfish.jersey.containers:jersey-container-servlet:jar:3.1.8:compile
[INFO] | +-
org.glassfish.jersey.containers:jersey-container-servlet-core:jar:3.1.8:compile
[INFO] |
It works with rs-api 4.0.0
Thanks for your help!
jakarta.ws.rs-api
4.0.0
Am Di., 10. Sept. 2024 um 20:27 Uhr schrieb Thomas Meyer :
>
> Hi,
>
> Looks correct, see example from GitHub:
>
> https://github.com/eclipse-ee4j/jersey/blob/3.1/examples/servlet3-webapp/pom.xml
>
> But I assume that Jerse
I had found about jersey-client, too, but it did not help.
The exceptions happen in static blocks, so no good information in the
stacktrace.
Am Di., 10. Sept. 2024 um 20:16 Uhr schrieb Sebastian Trost
:
>
> Jürgen,
>
> On 10.09.2024 20:07, Jürgen Weber wrote:
> > java.lang.ClassNotFoundException:
Hi,
Looks correct, see example from GitHub:
https://github.com/eclipse-ee4j/jersey/blob/3.1/examples/servlet3-webapp/pom.xml
But I assume that Jersey 3.1.x does implement jax-rs 3.1, so maybe that's the
reason it cannot find this class.
Mfg
Thomas
Am 10. September 2024 20:07:07 MESZ schrieb
Jürgen,
On 10.09.2024 20:07, Jürgen Weber wrote:
java.lang.ClassNotFoundException: org.glassfish.jersey.client.ClientConfig
java.lang.NoClassDefFoundError: jakarta/ws/rs/core/EntityPart
org.glassfish.jersey
jersey-bom
jakarta.ws.rs
jakarta.ws.rs-api
3.0.0
org.glassfish.jersey.containers
jers
