July 2020 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-13670) Remaining UX issues in readme for microprofile-fault-tolerance QS

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13670?page=com.atlassian.jira.plugi... ] Radoslav Husar moved JBEAP-19918 to WFLY-13670: ----------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-13670 (was: JBEAP-19918) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Quickstarts (was: Quickstarts) Affects Version/s: 20.0.1.Final 20.0.0.Final (was: EAP-XP-1.0.0.GA-CR1) > Remaining UX issues in readme for microprofile-fault-tolerance QS > ----------------------------------------------------------------- > > Key: WFLY-13670 > URL: https://issues.redhat.com/browse/WFLY-13670 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.1.Final, 20.0.0.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Major > > (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. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13670) Remaining UX issues in readme for microprofile-fault-tolerance QS

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13670?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13670: ---------------------------------- Priority: Optional (was: Major) > Remaining UX issues in readme for microprofile-fault-tolerance QS > ----------------------------------------------------------------- > > Key: WFLY-13670 > URL: https://issues.redhat.com/browse/WFLY-13670 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Optional > > (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. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13670) Remaining UX issues in readme for microprofile-fault-tolerance QS

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13670?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13670: ---------------------------------- Priority: Minor (was: Optional) > Remaining UX issues in readme for microprofile-fault-tolerance QS > ----------------------------------------------------------------- > > Key: WFLY-13670 > URL: https://issues.redhat.com/browse/WFLY-13670 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > (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. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13670) Remaining UX issues in readme for microprofile-fault-tolerance QS

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13670?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13670: ---------------------------------- Git Pull Request: (was: https://github.com/jbossas/eap-quickstarts/pull/168, https://github.com/jbossas/eap-quickstarts/pull/173) > Remaining UX issues in readme for microprofile-fault-tolerance QS > ----------------------------------------------------------------- > > Key: WFLY-13670 > URL: https://issues.redhat.com/browse/WFLY-13670 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > (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. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13670) Remaining UX issues in readme for microprofile-fault-tolerance QS

by Radoslav Husar (Jira)

[ https://issues.redhat.com/browse/WFLY-13670?page=com.atlassian.jira.plugi... ] Radoslav Husar updated WFLY-13670: ---------------------------------- Description: The 2 issues remaining are: (5) Prerequisites and System Requirements sections both mention JDK and Maven versions. While JDK is just a duplicate, Maven version does not match in two sections. If the Maven version in standard System Requirements section is too old we should consider updating it. (6) Build and Deploy the Quickstart section says "Make sure you start the JBoss EAP XP server as described above." and points to Start the JBoss EAP XP Standalone Server but this section is not above but below. Suggestion: move Start the JBoss EAP XP Standalone Server above Build and Deploy the Quickstart and then you can point to this section from Creating the Maven Project from sentence "Start a JBoss EAP XP instance using the microprofile server profile." 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. > Remaining UX issues in readme for microprofile-fault-tolerance QS > ----------------------------------------------------------------- > > Key: WFLY-13670 > URL: https://issues.redhat.com/browse/WFLY-13670 > Project: WildFly > Issue Type: Bug > Components: Quickstarts > Affects Versions: 20.0.0.Final, 20.0.1.Final > Reporter: Radoslav Husar > Assignee: Radoslav Husar > Priority: Minor > > The 2 issues remaining are: > (5) Prerequisites and System Requirements sections both mention JDK and Maven versions. While JDK is just a duplicate, Maven version does not match in two sections. If the Maven version in standard System Requirements section is too old we should consider updating it. > (6) Build and Deploy the Quickstart section says "Make sure you start the JBoss EAP XP server as described above." and points to Start the JBoss EAP XP Standalone Server but this section is not above but below. > Suggestion: move Start the JBoss EAP XP Standalone Server above Build and Deploy the Quickstart and then you can point to this section from Creating the Maven Project from sentence "Start a JBoss EAP XP instance using the microprofile server profile." -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13481) Upgrade wildfly-transaction-client to 1.1.12.Final

by Tomas Hofman (Jira)

[ https://issues.redhat.com/browse/WFLY-13481?page=com.atlassian.jira.plugi... ] Tomas Hofman resolved WFLY-13481. --------------------------------- Resolution: Out of Date > Upgrade wildfly-transaction-client to 1.1.12.Final > -------------------------------------------------- > > Key: WFLY-13481 > URL: https://issues.redhat.com/browse/WFLY-13481 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB, Transactions > Affects Versions: 19.1.0.Final > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Critical > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Release diff: https://github.com/wildfly/wildfly-transaction-client/compare/1.1.11.Fina... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13481) Upgrade wildfly-transaction-client to 1.1.12.Final

by Tomas Hofman (Jira)

[ https://issues.redhat.com/browse/WFLY-13481?page=com.atlassian.jira.plugi... ] Tomas Hofman commented on WFLY-13481: ------------------------------------- The fix in wildfly-transaction-client has been reverted. It was instead resolved by EJBCLIENT-373 / WFLY-13522. > Upgrade wildfly-transaction-client to 1.1.12.Final > -------------------------------------------------- > > Key: WFLY-13481 > URL: https://issues.redhat.com/browse/WFLY-13481 > Project: WildFly > Issue Type: Component Upgrade > Components: EJB, Transactions > Affects Versions: 19.1.0.Final > Reporter: Tomasz Adamski > Assignee: Tomasz Adamski > Priority: Critical > Labels: downstream_dependency > Fix For: 21.0.0.Beta1 > > > Release diff: https://github.com/wildfly/wildfly-transaction-client/compare/1.1.11.Fina... -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-13669) Warning in log when running Arquillian tests for MicroProfile REST client quickstart

by Martin Stefanko (Jira)

Martin Stefanko created WFLY-13669: -------------------------------------- Summary: Warning in log when running Arquillian tests for MicroProfile REST client quickstart Key: WFLY-13669 URL: https://issues.redhat.com/browse/WFLY-13669 Project: WildFly Issue Type: Bug Components: Quickstarts Affects Versions: 20.0.1.Final Reporter: Martin Stefanko Assignee: Martin Stefanko When running Arquilllian tests for MicroProfile REST client quickstart a WARN message appears in log: {noformat} WARN [org.wildfly.extension.undertow] (MSC service thread 1-4) WFLYUT0101: Duplicate servlet mapping /* found {noformat} -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-5317) Scenario Simulation shows misleading data type if DMN applies a constraint

by Yeser Amer (Jira)

[ https://issues.redhat.com/browse/DROOLS-5317?page=com.atlassian.jira.plug... ] Yeser Amer updated DROOLS-5317: ------------------------------- Priority: Major (was: Critical) > Scenario Simulation shows misleading data type if DMN applies a constraint > -------------------------------------------------------------------------- > > Key: DROOLS-5317 > URL: https://issues.redhat.com/browse/DROOLS-5317 > Project: Drools > Issue Type: Bug > Affects Versions: 7.37.0.Final > Reporter: Yeser Amer > Assignee: Yeser Amer > Priority: Major > Labels: drools-tools > -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-5051) server group deployment resource doesn't include correct "mananged" value

by Chao Wang (Jira)

Chao Wang created WFCORE-5051: --------------------------------- Summary: server group deployment resource doesn't include correct "mananged" value Key: WFCORE-5051 URL: https://issues.redhat.com/browse/WFCORE-5051 Project: WildFly Core Issue Type: Bug Components: Management Affects Versions: 13.0.0.Beta1 Reporter: Chao Wang Assignee: Chao Wang Unmanaged deploys show a checkmark that they are "managed" if you view the deployment under Server Groups. The deployment does however show correctly that it is un-managed in the Content Repository section. -- This message was sent by Atlassian Jira (v7.13.8#713008)

5 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira July 2020