[jboss-jira] [JBoss JIRA] (WFLY-13475) MP FT Quickstart: Change server startup documentation to reference local installation and standalone-microprofile.xml

Eduardo Martins (Jira) issues at jboss.org
Fri May 15 06:02:56 EDT 2020


     [ https://issues.redhat.com/browse/WFLY-13475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eduardo Martins updated WFLY-13475:
-----------------------------------
    Description: 
(1) WildFly pom is used instead of EAP XP one:
{code}
            <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". 
{code}
This is mentioned in JBEAP-19481 as well. 

(2) Unsupported commands for starting and managing EAP:
{code}
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
{code}

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

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

  was:
(1) WildFly pom is used instead of EAP XP one:
{code}
            <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". 
{code}
This is mentioned in JBEAP-19481 as well. 

(2) Unsupported commands for starting and managing EAP:
{code}
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
{code}

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



> MP FT Quickstart: Change server startup documentation to reference local installation and standalone-microprofile.xml
> ---------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-13475
>                 URL: https://issues.redhat.com/browse/WFLY-13475
>             Project: WildFly
>          Issue Type: Bug
>          Components: MP Fault Tolerance, Quickstarts
>    Affects Versions: 19.1.0.Final
>            Reporter: Radoslav Husar
>            Assignee: Radoslav Husar
>            Priority: Critical
>             Fix For: 20.0.0.Beta1
>
>
> (1) WildFly pom is used instead of EAP XP one:
> {code}
>             <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". 
> {code}
> This is mentioned in JBEAP-19481 as well. 
> (2) Unsupported commands for starting and managing EAP:
> {code}
> 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
> {code}
> (3) I think there's no need to add the subsystem if using standalone-microprofile.xml config where it is already present.
> There might be additional issues I don't see because of JBEAP-19481.



--
This message was sent by Atlassian Jira
(v7.13.8#713008)


More information about the jboss-jira mailing list