home.social

#jakartaee — Public Fediverse posts

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

  1. This week, it is IntelliJ IDEA Conference where I will present Jakarta EE

    CPH ✈️ AMS

    #JakartaEE #EclipseFoundation #Community

  2. This week, it is IntelliJ IDEA Conference where I will present Jakarta EE

    CPH ✈️ AMS

    #JakartaEE #EclipseFoundation #Community

  3. This week, it is IntelliJ IDEA Conference where I will present Jakarta EE

    CPH ✈️ AMS

    #JakartaEE #EclipseFoundation #Community

  4. This week, it is IntelliJ IDEA Conference where I will present Jakarta EE

    CPH ✈️ AMS

    #JakartaEE #EclipseFoundation #Community

  5. This week, it is IntelliJ IDEA Conference where I will present Jakarta EE

    CPH ✈️ AMS

    #JakartaEE #EclipseFoundation #Community

  6. Start with nothing. End with a secured Jakarta EE app. And live-code everything in between. 👨‍💻

    At #BaselOne26, @hannotify builds a RESTful app from scratch, secures it with JWT and connects an Angular frontend.

    JAX-RS, JPA, #MicroProfile, OpenAPI – with as much live coding as possible. And if things go wrong along the way? That’s part of the game. 😉

    👉 Full programme: baselone.org/#programm
    🎟️ Tickets: eventfrog.ch/BaselOne26

    #JakartaEE #Java #LiveCoding

  7. Start with nothing. End with a secured Jakarta EE app. And live-code everything in between. 👨‍💻

    At #BaselOne26, @hannotify builds a RESTful app from scratch, secures it with JWT and connects an Angular frontend.

    JAX-RS, JPA, #MicroProfile, OpenAPI – with as much live coding as possible. And if things go wrong along the way? That’s part of the game. 😉

    👉 Full programme: baselone.org/#programm
    🎟️ Tickets: eventfrog.ch/BaselOne26

    #JakartaEE #Java #LiveCoding

  8. Start with nothing. End with a secured Jakarta EE app. And live-code everything in between. 👨‍💻

    At #BaselOne26, @hannotify builds a RESTful app from scratch, secures it with JWT and connects an Angular frontend.

    JAX-RS, JPA, #MicroProfile, OpenAPI – with as much live coding as possible. And if things go wrong along the way? That’s part of the game. 😉

    👉 Full programme: baselone.org/#programm
    🎟️ Tickets: eventfrog.ch/BaselOne26

    #JakartaEE #Java #LiveCoding

  9. Start with nothing. End with a secured Jakarta EE app. And live-code everything in between. 👨‍💻

    At #BaselOne26, @hannotify builds a RESTful app from scratch, secures it with JWT and connects an Angular frontend.

    JAX-RS, JPA, #MicroProfile, OpenAPI – with as much live coding as possible. And if things go wrong along the way? That’s part of the game. 😉

    👉 Full programme: baselone.org/#programm
    🎟️ Tickets: eventfrog.ch/BaselOne26

    #JakartaEE #Java #LiveCoding

  10. Hashtag Jakarta EE number 349 is out!

    Read about a new Jakarta EE Core Profile implementation, Jakarta CDI 5.0, Jakarta Agentic AI, and JakartaOne Livestream CFP closing soon

    #JakartaEE #EclipseFoundation #Community

    agilejava.eu/2026/09/06/hashta

  11. Hashtag Jakarta EE number 349 is out!

    Read about a new Jakarta EE Core Profile implementation, Jakarta CDI 5.0, Jakarta Agentic AI, and JakartaOne Livestream CFP closing soon

    #JakartaEE #EclipseFoundation #Community

    agilejava.eu/2026/09/06/hashta

  12. Hashtag Jakarta EE number 349 is out!

    Read about a new Jakarta EE Core Profile implementation, Jakarta CDI 5.0, Jakarta Agentic AI, and JakartaOne Livestream CFP closing soon

    #JakartaEE #EclipseFoundation #Community

    agilejava.eu/2026/09/06/hashta

  13. Hashtag Jakarta EE number 349 is out!

    Read about a new Jakarta EE Core Profile implementation, Jakarta CDI 5.0, Jakarta Agentic AI, and JakartaOne Livestream CFP closing soon

    #JakartaEE #EclipseFoundation #Community

    agilejava.eu/2026/09/06/hashta

  14. Hashtag Jakarta EE number 349 is out!

    Read about a new Jakarta EE Core Profile implementation, Jakarta CDI 5.0, Jakarta Agentic AI, and JakartaOne Livestream CFP closing soon

    #JakartaEE #EclipseFoundation #Community

    agilejava.eu/2026/09/06/hashta

  15. 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

  16. 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

  17. 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

  18. 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

  19. 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

  20. 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

  21. 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

  22. 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

  23. 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

  24. 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

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

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

    habr.com/ru/articles/823836/

    #java #jakartaee #i18n #openliberty

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

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

    habr.com/ru/articles/823836/

    #java #jakartaee #i18n #openliberty

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

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

    habr.com/ru/articles/823836/

    #java #jakartaee #i18n #openliberty

  28. 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

  29. 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.

  30. 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

  31. 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

  32. 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