home.social

#openliberty — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #openliberty, aggregated by home.social.

fetched live
  1. Open Liberty's Maven documentation has all the pieces. The end-to-end path is spread across plugin goals, dev mode, feature installation, and packaging.

    I connected and validated that path with Java 21 and Jakarta REST 4.0: hot reload, Failsafe against a real server, a clean CI build, and a runnable JAR.

    the-main-thread.com/p/open-lib

    #Java #OpenLiberty #Maven #JakartaEE

  2. Open Liberty's Maven documentation has all the pieces. The end-to-end path is spread across plugin goals, dev mode, feature installation, and packaging.

    I connected and validated that path with Java 21 and Jakarta REST 4.0: hot reload, Failsafe against a real server, a clean CI build, and a runnable JAR.

    the-main-thread.com/p/open-lib

    #Java #OpenLiberty #Maven #JakartaEE

  3. Open Liberty's Maven documentation has all the pieces. The end-to-end path is spread across plugin goals, dev mode, feature installation, and packaging.

    I connected and validated that path with Java 21 and Jakarta REST 4.0: hot reload, Failsafe against a real server, a clean CI build, and a runnable JAR.

    the-main-thread.com/p/open-lib

    #Java #OpenLiberty #Maven #JakartaEE

  4. Open Liberty's Maven documentation has all the pieces. The end-to-end path is spread across plugin goals, dev mode, feature installation, and packaging.

    I connected and validated that path with Java 21 and Jakarta REST 4.0: hot reload, Failsafe against a real server, a clean CI build, and a runnable JAR.

    the-main-thread.com/p/open-lib

    #Java #OpenLiberty #Maven #JakartaEE

  5. Open Liberty's Maven documentation has all the pieces. The end-to-end path is spread across plugin goals, dev mode, feature installation, and packaging.

    I connected and validated that path with Java 21 and Jakarta REST 4.0: hot reload, Failsafe against a real server, a clean CI build, and a runnable JAR.

    the-main-thread.com/p/open-lib

    #Java #OpenLiberty #Maven #JakartaEE

  6. Avoiding upgrades reduces effort—but increases security risk. With breach costs at $4.4M, staying current matters. @gracejansen27 & Laura Cowen show how zero migration cuts friction.

    Learn how to stay secure without rewrites: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  7. Avoiding upgrades reduces effort—but increases security risk. With breach costs at $4.4M, staying current matters. @gracejansen27 & Laura Cowen show how zero migration cuts friction.

    Learn how to stay secure without rewrites: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  8. Runtime upgrades in enterprise #Java mean broken deps, code changes, testing. @gracejansen27 & Laura Cowen introduce “zero migration”—upgrade runtimes without touching code.

    See how apps move across 80+ releases unchanged: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  9. Runtime upgrades in enterprise #Java mean broken deps, code changes, testing. @gracejansen27 & Laura Cowen introduce “zero migration”—upgrade runtimes without touching code.

    See how apps move across 80+ releases unchanged: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  10. Avoiding upgrades reduces effort—but increases security risk. With breach costs at $4.4M, staying current matters. @gracejansen27 & Laura Cowen show how zero migration cuts friction.

    Learn how to stay secure without rewrites: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  11. Avoiding upgrades reduces effort—but increases security risk. With breach costs at $4.4M, staying current matters. @gracejansen27 & Laura Cowen show how zero migration cuts friction.

    Learn how to stay secure without rewrites: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  12. Runtime upgrades in enterprise #Java mean broken deps, code changes, testing. @gracejansen27 & Laura Cowen introduce “zero migration”—upgrade runtimes without touching code.

    See how apps move across 80+ releases unchanged: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  13. Runtime upgrades in enterprise #Java mean broken deps, code changes, testing. @gracejansen27 & Laura Cowen introduce “zero migration”—upgrade runtimes without touching code.

    See how apps move across 80+ releases unchanged: javapro.io/2026/04/10/zero-mig

    #OpenLiberty @OpenLibertyIO

  14. MicroProfile is not about annotations.
    It’s about contracts.

    In this hands-on guide, I build a book-catalog microservice with:
    • MicroProfile Config
    • Health (live + ready)
    • Fault Tolerance (timeout, retry, circuit breaker)
    • JWT security

    All on Open Liberty.
    No vendor APIs in business code.

    Production behavior included. Not just “it works locally.”

    the-main-thread.com/p/micropro

    #Java #MicroProfile #OpenLiberty #CloudNative #JakartaEE

  15. MicroProfile is not about annotations.
    It’s about contracts.

    In this hands-on guide, I build a book-catalog microservice with:
    • MicroProfile Config
    • Health (live + ready)
    • Fault Tolerance (timeout, retry, circuit breaker)
    • JWT security

    All on Open Liberty.
    No vendor APIs in business code.

    Production behavior included. Not just “it works locally.”

    the-main-thread.com/p/micropro

    #Java #MicroProfile #OpenLiberty #CloudNative #JakartaEE

  16. MicroProfile is not about annotations.
    It’s about contracts.

    In this hands-on guide, I build a book-catalog microservice with:
    • MicroProfile Config
    • Health (live + ready)
    • Fault Tolerance (timeout, retry, circuit breaker)
    • JWT security

    All on Open Liberty.
    No vendor APIs in business code.

    Production behavior included. Not just “it works locally.”

    the-main-thread.com/p/micropro

    #Java #MicroProfile #OpenLiberty #CloudNative #JakartaEE

  17. MicroProfile is not about annotations.
    It’s about contracts.

    In this hands-on guide, I build a book-catalog microservice with:
    • MicroProfile Config
    • Health (live + ready)
    • Fault Tolerance (timeout, retry, circuit breaker)
    • JWT security

    All on Open Liberty.
    No vendor APIs in business code.

    Production behavior included. Not just “it works locally.”

    the-main-thread.com/p/micropro

    #Java #MicroProfile #OpenLiberty #CloudNative #JakartaEE

  18. MicroProfile is not about annotations.
    It’s about contracts.

    In this hands-on guide, I build a book-catalog microservice with:
    • MicroProfile Config
    • Health (live + ready)
    • Fault Tolerance (timeout, retry, circuit breaker)
    • JWT security

    All on Open Liberty.
    No vendor APIs in business code.

    Production behavior included. Not just “it works locally.”

    the-main-thread.com/p/micropro

    #Java #MicroProfile #OpenLiberty #CloudNative #JakartaEE

  19. ⭐️⭐️⭐️ History and impact of the Internet Archive’s Open Library and Great 78 Project lawsuit losses #internetarchive #openliberty #copyright mastodon.social/@arstechnica/1

  20. ⭐️⭐️⭐️ History and impact of the Internet Archive’s Open Library and Great 78 Project lawsuit losses #internetarchive #openliberty #copyright mastodon.social/@arstechnica/1

  21. ⭐️⭐️⭐️ History and impact of the Internet Archive’s Open Library and Great 78 Project lawsuit losses #internetarchive #openliberty #copyright mastodon.social/@arstechnica/1

  22. ⭐️⭐️⭐️ History and impact of the Internet Archive’s Open Library and Great 78 Project lawsuit losses #internetarchive #openliberty #copyright mastodon.social/@arstechnica/1

  23. ⭐️⭐️⭐️ History and impact of the Internet Archive’s Open Library and Great 78 Project lawsuit losses #internetarchive #openliberty #copyright mastodon.social/@arstechnica/1

  24. Marcus Hellberg just delivered “Full-stack web apps, 100% Java” at #JCON USA @ #IBMTechXchange. A crisp live-coding tour of #OpenLiberty+ #Vaadin Flow—from persistence and external services to a good-looking UI—all in #Java!
    Bonus: it’s his birthday today 🎂 If you’re onsite, catch him in the hallway track and wish him well!

    #JCONUSA2025

  25. Marcus Hellberg just delivered “Full-stack web apps, 100% Java” at #JCON USA @ #IBMTechXchange. A crisp live-coding tour of #OpenLiberty+ #Vaadin Flow—from persistence and external services to a good-looking UI—all in #Java!
    Bonus: it’s his birthday today 🎂 If you’re onsite, catch him in the hallway track and wish him well!

    #JCONUSA2025

  26. Marcus Hellberg just delivered “Full-stack web apps, 100% Java” at #JCON USA @ #IBMTechXchange. A crisp live-coding tour of #OpenLiberty+ #Vaadin Flow—from persistence and external services to a good-looking UI—all in #Java!
    Bonus: it’s his birthday today 🎂 If you’re onsite, catch him in the hallway track and wish him well!

    #JCONUSA2025

  27. Marcus Hellberg just delivered “Full-stack web apps, 100% Java” at #JCON USA @ #IBMTechXchange. A crisp live-coding tour of #OpenLiberty+ #Vaadin Flow—from persistence and external services to a good-looking UI—all in #Java!
    Bonus: it’s his birthday today 🎂 If you’re onsite, catch him in the hallway track and wish him well!

    #JCONUSA2025

  28. Fed up with #JavaScript bugs? Take the red pill and build full-stack web apps with just #Java! 🕶️

    At #JCONUSA25, Marcus Hellberg will live-code apps using #OpenLiberty + #Vaadin Flow.
    100% Java, no agents, no glitches. Follow the white rabbit.

    usa.jcon.one/register

    #JCON #IBM #TechXchange

  29. Fed up with #JavaScript bugs? Take the red pill and build full-stack web apps with just #Java! 🕶️

    At #JCONUSA25, Marcus Hellberg will live-code apps using #OpenLiberty + #Vaadin Flow.
    100% Java, no agents, no glitches. Follow the white rabbit.

    usa.jcon.one/register

    #JCON #IBM #TechXchange

  30. Fed up with #JavaScript bugs? Take the red pill and build full-stack web apps with just #Java! 🕶️

    At #JCONUSA25, Marcus Hellberg will live-code apps using #OpenLiberty + #Vaadin Flow.
    100% Java, no agents, no glitches. Follow the white rabbit.

    usa.jcon.one/register

    #JCON #IBM #TechXchange

  31. Fed up with #JavaScript bugs? Take the red pill and build full-stack web apps with just #Java! 🕶️

    At #JCONUSA25, Marcus Hellberg will live-code apps using #OpenLiberty + #Vaadin Flow.
    100% Java, no agents, no glitches. Follow the white rabbit.

    usa.jcon.one/register

    #JCON #IBM #TechXchange

  32. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  33. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  34. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  35. Dive into the latest advancements in #Java with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

    #JDK21 #VirtualThreads #OpenLiberty

  36. Dive into the latest advancements in with our latest article on JDK 21's virtual threads: bit.ly/4cEppIA

    This analysis compares the performance of virtual threads with Open Liberty's thread pool, focusing on key findings such as throughput, ramp-up times, and memory footprint. While virtual threads offer several advantages, they also show unexpected performance issues, especially in CPU-intensive workloads.

    This analysis guides Java developers on when and how to use virtual threads in their applications.

  37. Нереальная локализация

    Давно хотелось раскрыть интересную тему локализации ПО, но так чтобы не повторяться и не цитировать прописные истины. Поэтому рассказываю как локализовать обычное корпоративное Java-приложение на.. несуществующие фантастические языки : Клингонский и Р’льех . Погрузиться

    habr.com/ru/articles/823836/

    #java #jakartaee #i18n #openliberty

  38. Нереальная локализация

    Давно хотелось раскрыть интересную тему локализации ПО, но так чтобы не повторяться и не цитировать прописные истины. Поэтому рассказываю как локализовать обычное корпоративное Java-приложение на.. несуществующие фантастические языки : Клингонский и Р’льех . Погрузиться

    habr.com/ru/articles/823836/

    #java #jakartaee #i18n #openliberty

  39. Нереальная локализация

    Давно хотелось раскрыть интересную тему локализации ПО, но так чтобы не повторяться и не цитировать прописные истины. Поэтому рассказываю как локализовать обычное корпоративное Java-приложение на.. несуществующие фантастические языки : Клингонский и Р’льех . Погрузиться

    habr.com/ru/articles/823836/

    #java #jakartaee #i18n #openliberty

  40. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  41. There has been some interesting discussion on 11 and servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.

  42. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  43. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  44. There has been some interesting discussion on #JakartaEE 11 and #Java servers over on Twitter. The draft of the spec has been updated to require JDK 17 rather than requiring JDK 21. I agree with the decision. To maximize adoption, JakartaEE must support JDK 17 and optionally JDK 21. Dropping JDK 11 is the best we can hope for right now.
    #JakartaEE11 #OpenJDK #OpenSource #JDK21 #JDK17 #JDK11 #WildFly #GlassFish #OpenLiberty #Tomcat #Jetty

  45. @kjjaeger
    #OpenJ9 and #OpenLiberty sounds like something @bmarwell is interested in. 😉

    Other than that maybe @javabubble can help to find some more contacts around #Java.

  46. @kjjaeger
    #OpenJ9 and #OpenLiberty sounds like something @bmarwell is interested in. 😉

    Other than that maybe @javabubble can help to find some more contacts around #Java.

  47. @kjjaeger
    and sounds like something @bmarwell is interested in. 😉

    Other than that maybe @javabubble can help to find some more contacts around .