Published latest aggregated blog posts

Author: jbossorg-bot

src/content/posts-aggregator/1.json

@@ -1,13 +1,13 @@
 {
-  "title": "Vlog: WildFly AI - monitor and troubleshoot a WildFly server with the WildFly chatbot.",
-  "link": "https://youtu.be/crSKeeBsXoE",
+  "title": "Quarkus 3.20 - new LTS version",
+  "link": "https://quarkus.io/blog/quarkus-3-20-0-released/",
   "author": [
     {
-      "name": "Jean-François Denise",
+      "name": "Guillaume Smet",
       "avatar": null
     }
   ],
-  "date": "2025-03-21T00:00:00.000Z",
-  "feed_title": "WildFly",
-  "content": "This video demonstrates how you can interact with a WildFly server using natural language."
+  "date": "2025-03-26T00:00:00.000Z",
+  "feed_title": "Quarkus",
+  "content": "It is our pleasure to announce the release of Quarkus 3.20, which is our new LTS (Long Term Support) version.  This version is built on the top of Quarkus 3.19 with some additional bugfixes. New features landed in Quarkus 3.21, which was also released today.  If you want to know more about our LTS policy, the is a must read.  LTS releases are supported for 12 months.  If you are coming from the previous LTS, Quarkus 3.15, there are a lot of exciting new features and we recommend reading the following announcements:   *    *    *    *    UPDATE  To update to Quarkus 3.20, we recommend updating to the latest version of the Quarkus CLI and run:  quarkus update  Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.20 LTS.  If you are upgrading from 3.19, there’s nothing to do as 3.20 is the direct continuation of 3.19.  If you are upgrading from the previous LTS, Quarkus 3.15, please refer to the following migration guides:   *    *    *    *    * - this one is empty as 3.20 is the continuation of 3.19  Note that quarkus update should handle most of the heavy lifting for you, but there are still cases that should be handled manually and we recommend reading these migration guides carefully.   WHAT’S NEW?   PLATFORM COMPONENT UPGRADES  CAMEL QUARKUS  Camel Quarkus has been updated to 3.20.0. You can find everything you need to know about it in the .  QUARKUS CXF  Quarkus CXF 3.20 was released and is now available in . Check the release notes for more information about what is new in this release.  AMAZON SERVICES  The Amazon Services extensions have been upgraded to version 3.3.1.   FULL CHANGELOG  The core part of Quarkus 3.20.0 is a rebadged release of Quarkus 3.19.4 so nothing new here.   CONTRIBUTORS  The Quarkus community is growing and has now . Many many thanks to each and everyone of them.  In particular for the 3.20 release, thanks to Ales Justin, Alexey Loubyansky, Andreas Maechler, Andy Damevin, Auri Munoz, brunobat, Clement Escoffier, cmoulliard, David Cotton, Dennis Kronbügel, Fabian, Foivos Zakkak, Georg Leber, George Gastaldi, Georgios Andrianakis, Guillaume Smet, Jakub Jedlicka, Jan Martiska, jcjveraa, Karm Michal Babacek, Katia Aresti, Ladislav Thon, Marco Belladelli, Martin Kouba, Martin Panzer, masecla22, Maximilian Zellhofer, melloware, Michal Maléř, Michal Vavřík, Ozan Gunalp, Peter Palaga, Phillip Kruger, Robert Stupp, Roberto Cortez, Rolfe Dlugy-Hegwer, Ryan Dens, Rüdiger zu Dohna, Sergey Beryozkin, shjones, Stephan Strate, Steve Hawkins, Stuart Douglas, Thomas Canava, w0pp, Welton Rodrigo Torres Nascimento, Willem Jan Glerum, xstefank, and Yoshikazu Nojima.  The list is a bit smaller than usual as 3.20 only contains bugfixes on top of 3.19.   COME JOIN US  We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together!  If you are a Quarkus user or just curious, don’t be shy and join our welcoming community:   * provide feedback on ;   * craft some code and ;   * discuss with us on and on the ;   * ask your questions on ."
 }

src/content/posts-aggregator/10.json

@@ -1,14 +1,13 @@
 {
-  "title": "Keycloak 26.1.4 released",
-  "link": "https://www.keycloak.org/2025/03/keycloak-2614-released",
+  "title": "Narayana and its relationship to Red Hat middleware strategy",
+  "link": "https://jbossts.blogspot.com/2025/03/narayana-and-its-relationship-to-red.html",
   "author": [
     {
-      "name": null,
+      "name": "Tom Jenkinson",
       "avatar": null
     }
   ],
-  "date": "2025-03-14T00:00:00.000Z",
-  "feed_title": "Keycloak Blog",
-  "feed_avatar": "https://www.gravatar.com/avatar/87fe00619f08c241da8dfb23d907ffa2?s=50",
-  "content": "To download the release go to .   UPGRADING  Before upgrading refer to for a complete list of changes.   ALL RESOLVED ISSUES   ENHANCEMENTS   * Allow admin to disable automatic refresh of event views admin/ui  * Upgrade to Infinispan 15.0.14   BUGS   * Cannot fetch realm role that was renamed admin/api  * When calling the token revoke endpoint multiple times with the same token, a    database REVOKED-TOKEN constraint error is reported storage  * Admin events: resource type filter does not work admin/ui  * Unwanted placeholder texts in user profile fields admin/ui  * KC_HTTPS_TRUST_STORE_TYPE not working dist/quarkus  * The default setting of the client request object parameter is empty admin/ui"
+  "date": "2025-03-17T16:55:00.001Z",
+  "feed_title": "Narayana team blog",
+  "content": "  Hi everyone,   You might have already seen that Red Hat announced significant changes to its middleware strategy last month (if not, please do check out the relevant “Red Hat Blog” article: Evolving our middleware strategy [1]) and so I want to speak a little to the change and its relevance to our Narayana project.   As you may know, Narayana is a part of a number of Red Hat products, in particular Red Hat’s JBoss Enterprise Application Platform product and so this makes the strategic decision relevant to the Narayana project. That said, a key point in that article from the “Red Hat Blog” with regards to our Narayana project is that all transitioning Red Hat technology will remain open source and continue to follow an upstream-first development model. So as well as the technology still relying on being able to upstream-first (in projects like Narayana), it’s also that this upstream should remain open source (you can find what open source means at Red Hat over here [2]). Not only is the Narayana source code open source, but moreover its project operates in an open source manner, exhibiting the principles of open source and gratefully benefits from a healthy community of users and contributors. This will help us to keep innovating in the area of transactions as we move forwards.   I will also take this opportunity to add a “Thank you” for being part of our Narayana community - I am excited to see the results of what we achieve together next!    Tom Jenkinson   [1] https://www.redhat.com/en/blog/evolving-our-middleware-strategy  [2] https://www.redhat.com/en/about/open-source "
 }

src/content/posts-aggregator/11.json

@@ -1,13 +1,14 @@
 {
-  "title": "Quarkus & Red Hat's evolving middleware strategy",
-  "link": "https://quarkus.io/blog/quarkus-redhat-strategy/",
+  "title": "Submit to KeyConf25 Japan Call-for-Papers!",
+  "link": "https://www.keycloak.org/2025/03/keyconf-25-japan-call-for-papers",
   "author": [
     {
-      "name": "Max Rydahl Andersen",
+      "name": "Alexander Schwartz",
       "avatar": null
     }
   ],
-  "date": "2025-03-13T00:00:00.000Z",
-  "feed_title": "Quarkus",
-  "content": "Over the past weeks, we’ve received questions about the that Red Hat’s Middleware engineering and product teams, which include Quarkus, are moving to IBM.  We want to take this opportunity to acknowledge this change while reaffirming what has always been true:  Quarkus is an open-source project driven by a global community of contributors, spanning companies, individuals, and open-source enthusiasts.  From its inception, Quarkus has been shaped by real-world adoption across industries, with companies , leveraging Quarkus’s unmatched performance and developer joy in the Java ecosystem. We recently celebrated our , a testament to the strength of this diverse and thriving community.  Speaking as Quarkus contributors employed by Red Hat and soon IBM, we love our project and intend to keep making it awesome. IBM and Red Hat have clearly communicated that the current and future contributions to Quarkus are a key component of the middleware strategy. IBM has already been an active contributor to Quarkus, and we look forward to increased contribution - alongside the many other individuals and companies who contribute, innovate, and drive Quarkus forward.  Additionally, Quarkus is already on the path to becoming part of an open-source foundation, further ensuring its long-term independence and success as a truly community-driven project. The move to the foundation and the Red Hat/IBM move could look suspicious timing-wise, but the two are unrelated. We described our reasons in a , but if anything, this announcement reaffirms the importance of a foundation-hosted project for its stability.  To our contributors and users: your involvement has always been what makes Quarkus thrive. Keep building, experimenting, and shaping the future of Java with us.  -- The Quarkus Team"
+  "date": "2025-03-17T00:00:00.000Z",
+  "feed_title": "Keycloak Blog",
+  "feed_avatar": "https://www.gravatar.com/avatar/87fe00619f08c241da8dfb23d907ffa2?s=50",
+  "content": "The call for papers for is now open! Submit your talks to the first-ever KeyConf in Japan.  KeyConf 2025 Japan is a free half-day meetup in Tokyo, Japan on June 13 where the community of Keycloak gathers. It provides opportunities for technical lectures, growth, and networking with talks related Identity and Access Management (IAM) and Single Sign On (SSO).  This event is designed to share insights from developers and maintainers, as well as the latest features, updates, and real-world use cases of Keycloak. Participants will have the valuable opportunity to interact directly with Keycloak experts and other users, deepening their knowledge.     RELATED EVENTS  A few days later, on June 16-17, takes place in Tokyo as well. The Keycloak team will be on-site for KubeCon Japan, so join us and a lot of other CNCF projects for this event as well.  See you in Tokyo!"
 }

src/content/posts-aggregator/12.json

@@ -1,13 +1,13 @@
 {
-  "title": "Quarkus 3.19.3 - Maintenance release",
-  "link": "https://quarkus.io/blog/quarkus-3-19-3-released/",
+  "title": "Quarkus & Red Hat's evolving middleware strategy",
+  "link": "https://quarkus.io/blog/quarkus-redhat-strategy/",
   "author": [
     {
-      "name": "Guillaume Smet",
+      "name": "Max Rydahl Andersen",
       "avatar": null
     }
   ],
-  "date": "2025-03-12T00:00:00.000Z",
+  "date": "2025-03-13T00:00:00.000Z",
   "feed_title": "Quarkus",
-  "content": "We released Quarkus 3.19.3, the second (we skipped 3.19.0) maintenance release for our 3.19 release train.  We also released two candidate releases:   * Quarkus 3.20.0.CR1 LTS - it is going to be our next LTS, it is based on 3.19   * Quarkus 3.21.0.CR1 - a regular minor release with new features   UPDATE  To update to Quarkus 3.19, we recommend updating to the latest version of the Quarkus CLI and run:  quarkus update  Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.19.  For more information about the adjustments you need to make to your applications, please refer to the .   FULL CHANGELOG  You can get the full changelog of on GitHub.   COME JOIN US  We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together!  If you are a Quarkus user or just curious, don’t be shy and join our welcoming community:   * provide feedback on ;   * craft some code and ;   * discuss with us on and on the ;   * ask your questions on ."
+  "content": "Over the past weeks, we’ve received questions about the that Red Hat’s Middleware engineering and product teams, which include Quarkus, are moving to IBM.  We want to take this opportunity to acknowledge this change while reaffirming what has always been true:  Quarkus is an open-source project driven by a global community of contributors, spanning companies, individuals, and open-source enthusiasts.  From its inception, Quarkus has been shaped by real-world adoption across industries, with companies , leveraging Quarkus’s unmatched performance and developer joy in the Java ecosystem. We recently celebrated our , a testament to the strength of this diverse and thriving community.  Speaking as Quarkus contributors employed by Red Hat and soon IBM, we love our project and intend to keep making it awesome. IBM and Red Hat have clearly communicated that the current and future contributions to Quarkus are a key component of the middleware strategy. IBM has already been an active contributor to Quarkus, and we look forward to increased contribution - alongside the many other individuals and companies who contribute, innovate, and drive Quarkus forward.  Additionally, Quarkus is already on the path to becoming part of an open-source foundation, further ensuring its long-term independence and success as a truly community-driven project. The move to the foundation and the Red Hat/IBM move could look suspicious timing-wise, but the two are unrelated. We described our reasons in a , but if anything, this announcement reaffirms the importance of a foundation-hosted project for its stability.  To our contributors and users: your involvement has always been what makes Quarkus thrive. Keep building, experimenting, and shaping the future of Java with us.  -- The Quarkus Team"
 }

src/content/posts-aggregator/13.json

@@ -1,13 +1,13 @@
 {
-  "title": "Running SQLite in Pure Java with Quarkus",
-  "link": "https://quarkus.io/blog/sqlite4j-pure-java-sqlite/",
+  "title": "Quarkus 3.19.3 - Maintenance release",
+  "link": "https://quarkus.io/blog/quarkus-3-19-3-released/",
   "author": [
     {
-      "name": "Andrea Peruffo",
+      "name": "Guillaume Smet",
       "avatar": null
     }
   ],
   "date": "2025-03-12T00:00:00.000Z",
   "feed_title": "Quarkus",
-  "content": "What if you could run a C-based database in pure Java, with zero configuration, and even compile it to a native image effortlessly? With the new Quarkiverse extension , you can do exactly that.  Traditionally, embedded databases in Java require reimplementing their C counterparts, often leading to differences in behavior, missing optimizations, and delayed bug fixes. However, provides a JDBC driver that leverages the original SQLite C implementation while running safely inside a sandbox.   HANDS-ON EXAMPLE  To see in action, you can start with any existing Quarkus application or one of the . If you prefer a ready-made example, check out , which integrates SQLite within a Quarkus application using Hibernate ORM.  By simply changing the JDBC driver dependency, you can embed a fully functional SQLite database inside your application while retaining all the benefits of the native SQLite implementation.  To get started, add the extension dependency to your pom.xml:  <dependency>     <groupId>io.quarkiverse.jdbc</groupId>     <artifactId>quarkus-jdbc-sqlite4j</artifactId> </dependency>  Then, configure your Quarkus application to use SQLite with standard JDBC settings:  quarkus.datasource.db-kind=sqlite quarkus.datasource.jdbc.url=jdbc:sqlite:sample.db quarkus.datasource.jdbc.min-size=1  You can now use your datasource as you normally would with Hibernate and Panache. Note that we keep a minimum connection pool size > 0 to avoid redundant copies from disk to memory of the database.   RUNNING IN A SECURE SANDBOX  Under the hood, SQLite runs in a fully in-memory sandboxed environment, ensuring security and isolation.    When a connection to a local file is opened, the following occurs:   1. The database file is copied from disk to an in-memory Virtual FileSystem.   2. A connection is established to the in-memory database.  While this approach is highly secure, many users need to persist database changes. One recommended solution is to periodically back up the in-memory database to disk. This can be achieved through a scheduled job that:   1. Backs up the in-memory database to a new file.   2. Copies the backup to the host file system.   3. Atomically replaces the old database file with the new backup.  This setup ensures a seamless experience while maintaining SQLite’s sandboxed security. You can adapt this approach to fit your specific needs.  Here’s a sample implementation:  @ApplicationScoped public class SQLiteBackup {     @ConfigProperty(name = \"quarkus.datasource.jdbc.url\")     String jdbcUrl;      @Inject     AgroalDataSource dataSource;      // Execute a backup every 10 seconds     @Scheduled(delay=10, delayUnit=TimeUnit.SECONDS, every=\"10s\")     void scheduled() { backup(); }      // Execute a backup during shutdown     public void onShutdown(@Observes ShutdownEvent event) { backup(); }      void backup() {         String dbFile = jdbcUrl.substring(\"jdbc:sqlite:\".length());          var originalDbFilePath = Paths.get(dbFile);         var backupDbFilePath = originalDbFilePath                                     .toAbsolutePath()                                     .getParent()                                     .resolve(originalDbFilePath.getFileName() + \"_backup\");          try (var conn = dataSource.getConnection();                 var stmt = conn.createStatement()) {             // Execute the backup             stmt.executeUpdate(\"backup to \" + backupDbFilePath);             // Atomically replace the DB file with its backup             Files.move(backupDbFilePath, originalDbFilePath,                 StandardCopyOption.ATOMIC_MOVE,                 StandardCopyOption.REPLACE_EXISTING);         } catch (IOException | SQLException e) {             throw new RuntimeException(\"Failed to back up the database\", e);         }     } }   TECHNICAL DEEP DIVE  compiles the official SQLite C to WebAssembly (Wasm), which is then translated into Java bytecode using the . This enables SQLite to run in a pure Java environment while maintaining its full functionality.     SECURITY AND ISOLATION  One of the key benefits of this approach is security. Running SQLite inside a Wasm sandbox ensures memory safety and isolates it from the host system, making it an excellent choice for applications that require embedded databases while avoiding the risks of native code execution.   CONCLUSION  With the new extension, you get the best of both worlds: the power and reliability of SQLite combined with the safety and portability of Java. This extension seamlessly integrates SQLite into Quarkus applications while maintaining a lightweight and secure architecture. Best of all, everything compiles effortlessly with native-image.  Ready to try it out? Give a spin in your projects and experience the benefits of running SQLite in pure Java with Quarkus!   PRIOR ART   *    * "
+  "content": "We released Quarkus 3.19.3, the second (we skipped 3.19.0) maintenance release for our 3.19 release train.  We also released two candidate releases:   * Quarkus 3.20.0.CR1 LTS - it is going to be our next LTS, it is based on 3.19   * Quarkus 3.21.0.CR1 - a regular minor release with new features   UPDATE  To update to Quarkus 3.19, we recommend updating to the latest version of the Quarkus CLI and run:  quarkus update  Note that quarkus update can update your applications from any version of Quarkus (including 2.x) to Quarkus 3.19.  For more information about the adjustments you need to make to your applications, please refer to the .   FULL CHANGELOG  You can get the full changelog of on GitHub.   COME JOIN US  We value your feedback a lot so please report bugs, ask for improvements… Let’s build something great together!  If you are a Quarkus user or just curious, don’t be shy and join our welcoming community:   * provide feedback on ;   * craft some code and ;   * discuss with us on and on the ;   * ask your questions on ."
 }