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

Issues in readme for microprofile-fault-tolerance QS

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • EAP-XP-1.0.1.CR2
    • EAP-XP-1.0.0.GA-CR1
    • Quickstarts
    • None

      (1) WildFly pom is used instead of EAP XP one:

                  <groupId>org.wildfly.bom</groupId>
            <artifactId>wildfly-microprofile</artifactId>
            <version>${version.server.bom}</version>
where ${version.server.bom} is the version of your JBoss EAP XP, in our case "1.0".

      This is mentioned in JBEAP-19481 as well.

      (2) Unsupported commands for starting and managing EAP:

      mvn wildfly:run &
mvn wildfly:execute-commands -Dwildfly.commands=/extension=org.wildfly.extension.microprofile.fault-tolerance-smallrye:add
mvn wildfly:execute-commands -Dwildfly.commands=/subsystem=microprofile-fault-tolerance-smallrye:add
mvn wildfly:shutdown -Dwildfly.reload=true

      (3) I think there's no need to add the subsystem if using standalone-microprofile.xml config where it is already present.

      (4) Consider adding standard sections - see other QS

      • Use of the EAP_HOME and QUICKSTART_HOME Variables
      • Start the JBoss EAP XP Standalone Server
      • Build and Deploy the Quickstart
      • Access the Application
      • Undeploy the Quickstart
      • Run the Quickstart in Red Hat JBoss Developer Studio or Eclipse

      There might be additional issues I don't see because of JBEAP-19481.

              rhn-engineering-rhusar Radoslav Husar
              nziakova@redhat.com Nikoleta Ziakova (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: