pulsar-jms VS jakartaee9-starter-boilerplate

While Pulsar has its own protocol that handles streaming, queues, and a lot of the other features (distributed transactions, functions, etc.), it can also speak other messaging protocols via plug-ins. Looking around, the ones that appear to be actively developed are MQTT, Kafka (so your existing applications that use Kafka can also use Pulsar), AMQP, and JMS.

Github is easy to share codes with others, for example I created jakartaee9-starter-boilerplate as a project template for Jakarta EE developers. For those who are familiar with Github, it is easy to start their new projects by forking or cloning this project directly. But obviously for a general Jakarta EE application, you do not need the configuraitons of all application severs, eg. Glassfish/Payara, WildFly, OpenLiberty, Apache TomEE, etc. For most of Java developers esp. Maven users, a simple and clean Maven archetype is still the preferred option to generate the new project skeleton, and you can add the required configuration back later.

jakartaee9-starter-boilerplate repository was created for developers who want to build a Jakarta EE 9 project. It was suggested to create a Maven archetype as a start point. This post describes how to generate a Jakarta EE 9 project skeleton from Maven archetype.

After it is done, the docs for the repository are available via http://hantsy.github.io/ , eg. https://hantsy.github.io/jakartaee9-starter-boilerplate/ is the online docs address for the repository hantsy/jakartaee9-starter-boilerplate.