Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-22093

Use `standalone-microprofile.xml` in MicroProfile quickstarts by default

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP-XP-3.0.0.CR1
    • None
    • Quickstarts
    • None

      Since the JBoss EAP 7.4.0.GA removed support for MicroProfile and as such removed appropriate subsystems from the default `standalone.xml` configuration, we shall probably use a `standalone-microprofile.xml` configuration file as a default one for all the MicroProfile JBoss EAP XP QuickStarts in their documentation.

      At the moment, some of the MicroProfile quickstarts already use `standalone-microprofile.xml` in their steps (fault-tolerance, jwt, openapi), others use the default `standalone.xml`. It would be nice to unify these as some may have problem to work correctly since the relevant subsystem is missing in the default `standalone.xml` configuration in JBoss EAP 7.4.0. Another approach would be to use some steps/scripts to configure necessary subsystems into the `standalone.xml` configuration as part of the deploy steps as `microprofile-reactive-messaging-kafka` does.

      Note: since there is not an official JBoss EAP XP 3.y.z release of quickstarts yet, I'm commenting based on the QuickStarts release provided for WildFly 24.0.0.Beta1 (simple diff didn't show any significant differences in relevant README.adoc files).

              chaowan@redhat.com Chao Wang
              jstourac@redhat.com Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: