v4.0.0 #6931
Replies: 6 comments 9 replies
-
|
I just upgraded 2 projects from 2.0.x and 2.1.x to 4.0.0. The migration was a breeze, no problems at all. Note: If you are using the dependency "swagger-jaxrs2", use the artifact "swagger-jaxrs2-jakarta" instead. |
Beta Was this translation helpful? Give feedback.
-
|
I just noticed this warning when starting the service: Might be a bug in Hibernate Validator: https://hibernate.atlassian.net/browse/HV-1852 Setting the "parameters" option in the Maven Compiler Plugin as suggested on StackOverflow doesn't fix it. Do you think we can safely ignore this warning? |
Beta Was this translation helpful? Give feedback.
-
|
Just checked: I get the same warning when I spin up the HelloWorldApplication from dropwizard-example (using OpenJDK Runtime Environment Temurin-11.0.17+8) |
Beta Was this translation helpful? Give feedback.
-
|
Hello. I'm a bit confused if dropwizard 4.0 has jetty 10 or 11. It looks like 11 but this part got copied from 3.0 release and not updated for 4.0. Am I assuming it right? |
Beta Was this translation helpful? Give feedback.
-
|
@natan-abolafya Yes, you are absolutely correct! This being said, the only difference between Jetty 10 and 11 is the usage of the Jakarta EE namespace. See also https://webtide.com/jetty-10-and-11-have-arrived/
|
Beta Was this translation helpful? Give feedback.
-
|
Great, thanks! Really appreciate the move with 3.0 and 4.0 by the way. Makes the upgrade step by step easier. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for your continuous efforts and latest improvements to Dropwizard. While trying to upgrade from an older version, I ran into a problem with logging. My build.gradle contains dropwizard-logging 4.0.0 as a dependency. The problem is that the server immediately terminates with the following exception: The referenced slfj4 docs state that placing one of slf4j-nop.jar, slf4j-simple.jar, slf4j-log4j12.jar, slf4j-jdk14.jar or logback-classic.jar should solve the problem. I tried adding several of them (one at a time) as a dependency to my build.gradle, but keep getting the same exception. Is there a simple solution, without resorting to external logging? |
Beta Was this translation helpful? Give feedback.
-
|
Hi @btlorch. The Dropwizard internally uses Logback as the default SLF4J implementation. So I'd suggest plaching logback-classic (version 1.4.x) on your classpath. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the explanation! It turned out that one of my dependencies was a JAR file that included SLF4J 1.7. Recompiling the JAR file with SLF4J excluded solve it for me. |
Beta Was this translation helpful? Give feedback.
-
|
Hi dropwizard dudes, ;) we just noticed that the dropwizard-gelf AppenderFactory (https://github.com/gini/dropwizard-gelf) is not loaded anymore in DW4, so we can't configure logging against Graylog. Is that to be expected? And what would be ways around that? Any input is appreciated. Thanks, |
Beta Was this translation helpful? Give feedback.
-
|
The last version of dropwizard-gelf was released for Dropwizard 2.0.x which itself is EOL since January 31, 2023. Since this project mostly a wrapper around https://github.com/mp911de/logstash-gelf, you could use the Logback appender of that project directly. Other than that, using https://github.com/logfellow/logstash-logback-encoder might also be a viable alternative to get logs into Graylog (Raw TCP input and parse and flatten the JSON payload). |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the reply. It seems like many of the Java projects supporting GELF have gone out of fashion. logstash-gelf is also unsupported as of last month and the last release has a few CVEs in its the dependencies. Thanks for the hint regarding logstash-logback-encoder, I will look into that. But maybe it's not really best practice anymore to log directly to Graylog from the Java service? I will also look into using a collector sidecar instead. Cheers |
Beta Was this translation helpful? Give feedback.
-
|
Hello dropwizard team! We are currently in the process of moving from Dropwizard 2 -> Dropwizard 4. We noticed that our When upgraded to Dropwizard 4 no longer seems to throw an exception when the function is called with a null parameter Trying to debug this issue has been tough as reading the documentation it seems that it would be expected that this would work out of the box https://www.dropwizard.io/en/stable/manual/validation.html We have tried to use the @NotNull annotation that belongs to the jakarta.validation library but that too seems to not be plumbed together. An observation we had is that Dropwizard 4.0 now uses hibernate-validator version 8.0.1.Final but the release notes say that Dropwizard is compatible with hibernate 6. https://www.dropwizard.io/en/stable/manual/upgrade-notes/upgrade-notes-4_0_x.html It looks like the Environment.getValidator() returns a jakarta.Validator and that the hibernate-validator 8 also accepts this so it doesnt look like there is an issues here. Another observation is that dropwizard 4 looks like its using JakartaEE 9 and hibernate 8 seems to support Jakarta 10. Hibernate 7 uses JakartaEE 9 but overriding the build file to use it doesnt solve the issue Has anyone had any issues similar to the one we are facing? And if they have is there a known issue? If not is there configuration code I can be pointed towards where these annotations would be configured at run time so I can take a deeper look there into what may be happening. Thanks! |
Beta Was this translation helpful? Give feedback.
-
|
Hi @Sachin-Bhararti. To validate objects, you should use the The release notes only refer to the term 'Hibernate'. This is commonly used for the Hibernate ORM database library. Hibernate Validator will always be refered to with the term 'Hibernate Validator'. That being said, Dropwizard 4.0.x is compatible with Hibernate ORM 6.1 and not Hibernate Validator 6.1. The artifact of Hibernate Validator is currently shipped with the version |
Beta Was this translation helpful? Give feedback.
-
|
Updating to 7.0.5 resolved this issue for us |
Beta Was this translation helpful? Give feedback.
-
Dropwizard 4.0.0
It's finally here, the next major release of Dropwizard! This one has been developed and released in tandem with Dropwizard 3.0.0.
If you're wondering what the differences are: Not much!
3️⃣ Dropwizard 3.0.0 is still based on and is using dependencies for Java EE and the
javax.*package namespace. The effort to migrate from Dropwizard 2.x to Dropwizard 3.0.0 should be minimal for many projects.4️⃣ Dropwizard 4.0.0 is based on and is using dependencies for Jakarta EE and the
jakarta.*package namespace. The effort to migrate from Dropwizard 2.x to Dropwizard 4.0.0 might be bigger due to more package changes and more breaking changes in our dependencies.📣 In any case, let us know how the migration went and if you were missing anything important in the upgrade notes in our GitHub Discussions!
For a full list of relevant changes please refer to the Upgrade Notes for Dropwizard 4.0.x.
Java 11 baseline
Dropwizard 4.0.0 and later require Java 11 as a baseline. Later versions of Java are also working.
Dropwizard Package Structure and JPMS
In order to properly support the Java Platform Module System (JPMS), the Java packages in modules must not overlap, or put differently, the packages may not be split into multiple modules.
Dropwizard 4.0.0 won’t enable full support for the JPMS. Instead, as a transition step, automatic modules are introduced.
Affected packages:
dropwizard-coreio.dropwizardio.drowizard.coredropwizard-loggingio.dropwizard.loggingio.dropwizard.logging.commondropwizard-metricsio.dropwizard.metricsio.dropwizard.metrics.commondropwizard-viewsio.dropwizard.viewsio.dropwizard.views.commonTransition to Jakarta EE
Previously released Dropwizard versions used Java/Jakarta EE dependencies under the
javaxnamespace. Dropwizard 4.0.x transitioned to Jakarta EE 9 components and therefore utilize the newjakartanamespace for many components.This means that most of the imports of existing applications using Dropwizard 2.x or 3.x will have to be changed from the
javaxto thejakartanamespace. However, other components still use thejavaxnamespace, so a simple search and replace could break other imports.Jakarta EE 9 compatibility
As stated above, Dropwizard 4.0.x will transition to Jakarta EE 9 components. This means, Dropwizard will now try to be consistent with one specific EE version.
Therefore Dropwizard 4.0.x will stay on components of Jakarta EE 9 and the transition to components of Jakarta EE 10 will be postponed to an other release series.
Since the EE version bump will probably introduce breaking changes, the Jakarta EE 10 components will be most likely integrated in Dropwizard 5.0.x and not in a 4.1.x release.
Jetty 11
The main change introduced in Dropwizard 4.0.0 is the upgrade to Jetty 11.0.x. Jetty 11.0.x is built for Java 11, therefore the Java version change was necessary.
This change comes with some migration cost. For detailed information regarding the changes introduced in Jetty 11.0.x, refer to the Jetty migration guide.
Apache HttpClient 5
The version of Apache HttpClient used in dropwizard-client has been updated to version 5.x.
For more information refer to the Apache HttpClient 5.0 migration guide.
Hibernate 6
Hibernate 5.6 provides compatible implementations for JPA 2.2 and for Jakarta Persistence 3.0.
But Hibernate 6.0 and 6.1 still provide compatible implementations for Jakarta Persistence 3.0, so we upgraded to Hibernate 6.1 in Dropwizard 4.0.x.
If any other aspects from Hibernate are used in an application rather than those provided by Dropwizard, there might be an additional migration cost. Please follow the Hibernate 6 migration guide and the Hibernate 6.1 migration guide, if you encounter any problems.
Removed Support for JUnit 4.x
Support for testing with JUnit 4.x has been moved from
dropwizard-testingto dropwizard-testing-junit4.🥇 Special thanks
The release of Dropwizard 3.0.0 wouldn't have been possible without the help of the community (YOU!) and especially the following contributors:
@zUniQueX, @rhowe, @pstackle, @dennyac, and countless others!
What's Changed since Dropwizard 4.0.0-beta.4
Full Changelog: v4.0.0-beta.4...v4.0.0
This discussion was created from the release v4.0.0.
Beta Was this translation helpful? Give feedback.
All reactions