- Random notes/links/tips to help share Quarkus related info with team
- https://quarkus.io/
- Installing Quarkus via https://sdkman.io/
- https://developers.redhat.com/blog/2020/09/11/quarkus-and-jakarta-ee-together-or-not
- https://kubebyexample.com/learning-paths/developing-quarkus-kubernetes/getting-started-quarkus/introduction
- https://quarkus.io/guides/cdi
- https://jakarta.ee/specifications/cdi/4.0/jakarta-cdi-spec-4.0.html#introduction
- EJB related
- https://quarkus.io/blog/on-the-road-to-cdi-compatibility/
- https://openliberty.io/guides/cdi-intro.html
- https://quarkus.io/guides/getting-started-reactive
- https://developers.redhat.com/coderland/reactive/reactive-intro
- Messaging with Quarkus – part one: JMS Messaging
- Messaging with Quarkus – part two: Reactive Messaging
- Getting Started with Java Message Service (JMS)
- https://developers.redhat.com/blog/2019/11/07/quarkus-modernize-helloworld-jboss-eap-quickstart-part-1?source=sso
- https://developers.redhat.com/blog/2019/04/12/migrating-java-applications-to-quarkus-lessons-learned
- Installing JDK via https://sdkman.io/
- Quarkus needs to build with minimal of JDK 11
- Quarkus doesn't have a MDB (Message Driven Bean) message consumption can be simulated using a CDI Bean. Below example shows a JMSConsumer Bean scheduling an event every 5 seconds that will check for incoming messages in the JMS Queue:
- Jakarta EE 9 is mostly a rename of Java EE 8 to Jakarta, so the bulk of changes will be import changes to
jakarta.*without additional features