jaxrs-api | Jaxrs

We are building an app based on Red Hat JBoss AMQ 6. We wrap some Java code around the base image to provide extra functionalities which are lacking in AMQ 6.

Now, when the CVE of Log4j stroke, we found that this component is vulnerable because it uses log4j 1.x. Now I don't just mean our Java code uses it, but also the base image of Red Hat AMQ 6 uses it. As AMQ 6 is EOL now, Red Hat does not provide support anymore, so there will not be official releases with fix.

So, how do I remove vulnerable log4j 1.x classes from:

• my Java code
• the base image

?

I am building with jib maven plugin.

It seems mvn dependency:tree only gives info about our Java wrapper code, not about the base image. And I don't understand what does the "+" and "-" mean while it gives output like this:

I am experimenting with Javax/JaxRs and I am using the WildFly 25 server, which I am not quite familiar with.

Searching for something similar to Spring's Actuator, I stumbled across the metrics & health endpoints the server exposes by default, and its ability to add custom counters, gauges etc. to application endpoints.

However, whatever I do, these custom endpoints are not exposed under the default http://localhost:9990/metrics URL.

I am following the guide provided by WildFly under the GitHub repository: https://github.com/wildfly/quickstart/tree/main/microprofile-metrics

There are some "red flags" on the tutorial that do not seem to be working with whatever I try to do.

1. The guide suggests that if we want to get the metrics in JSON format, we need to use the following header: "Accepted: application/json", which still returns the default Prometheus format, both in Postman and Curl.
2. The guide also suggests that metrics/vendor, metrics/application, metrics/base return metrics of different scopes, which to my test, they all return the same.

As far as the tutorial code is concerned, I tried running it on the Jakarta EE 8 Full & Web Distribution but it throws the following error:

Artifact microprofile-metrics:war exploded: java.lang.Exception: {"WFLYCTL0080: Failed services" => {"jboss.deployment.unit.\"microprofile-metrics.war\".undertow-deployment" => "java.lang.NoClassDefFoundError: org/eclipse/microprofile/metrics/Counter Caused by: java.lang.NoClassDefFoundError: org/eclipse/microprofile/metrics/Counter

I tried compiling the code with different versions of Java (1.8, 11, 17) hoping that it may fix the problem but to no avail.

However, using the WildFly Preview EE 9.1 Distribution seems to stop throwing the error, but the custom metrics still do not to work.

There are the subsystems that I added to both distributions during my tries (taken from standalone.xml):

I recently updated the Keycloak client libraries used by by project to version 14.0.0. I have a test is failing with the following:

So I have a Spring boot application that runs on port 8080 on my localhost. It connects to an Azure sqlserver database and pulls or inserts item from that database. Locally everything is working fine. Now I'm trying to dockerize the application. My Dockerfile looks like this:

first Sorry for my bulky source code and simple question.

I get this error.

javax.ws.rs.ProcessingException: RESTEASY003215: could not find writer for content-type application/json type: com.acme.customers.lib.v1.Customer

Complete Trace:

Running test in IDEA succeeds but when I try mvn clean test -Premote (or -Plocal) from command line fails with this exception:

I am using the latest stable version of quite standard Java libraries such as Spring, yet get 'overlapping classes' warning from maven shade plugin about 3 (three) different libraries that define the same classes.

The libraries: jakarta.activation-api, javax.activation-api, activation.

Specifically:

1. jakarta.activation:jakarta.activation-api:jar:1.2.2 (dependency of jakarta.xml.bind:jakarta.xml.bind-api:jar:2.3.3)
2. javax.activation:javax.activation-api:jar:1.2.0 (dependency of javax.xml.bind:jaxb-api:jar:2.3.1, I think this one should be replaced by jakarta.xml.bind-api, but not sure)
3. javax.activation:activation:jar:1.1 (dependency of com.sun.mail:javax.mail:jar:1.6.2)

What library is the 'right' one that will cause the least amount of trouble?

Update: it seems that jakarta.xml.bind-api replaces javax.xml.bind:jaxb-api (proof: here and here), so in the conflict between (1) and (2) the jakarta one (jakarta.activation-api) should be preferred over the javax one (javax.activation-api). The preferred JAXB dependencies are described in Jakarta web site. But it is still unclear how is this related to javax.activation:activation.

If I try to compile my webapp with mvn clean install -U I get the errorlog below.

I am building my first Jakarta ee 8 App. Actually I come from Spring-Framework background, so I am focusing on the key differences and best practices. I read that Glassfish, Wildfly, JBoss EAP etc. provide implementations to the Jakarta ee Specifications. This raised the question: