April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Gabriele Cardosi (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Gabriele Cardosi commented on DROOLS-3674: ------------------------------------------ [~zhutaojiajia] Ok, I'll do with "hover" and see how it will work > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3591) [DMN Designer] Data Types - Type dropdown is not navigable by keyboard

by Jozef Marko (Jira)

[ https://issues.jboss.org/browse/DROOLS-3591?page=com.atlassian.jira.plugi... ] Jozef Marko updated DROOLS-3591: -------------------------------- Tester: Jozef Marko > [DMN Designer] Data Types - Type dropdown is not navigable by keyboard > ---------------------------------------------------------------------- > > Key: DROOLS-3591 > URL: https://issues.jboss.org/browse/DROOLS-3591 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.18.0.Final > Reporter: Guilherme Gomes > Assignee: Daniel José dos Santos > Priority: Major > Labels: drools-tools > Attachments: 2019-01-31 15.02.26.gif > > > The following navigation between types must work in all supported browsers: > !2019-01-31 15.02.26.gif|thumbnail! > [~tirelli] reported that in some scenarios this navigation doesn't work. > --- > *Steps to reproduce:* > - Add new DT > - Insert the name > - Dropdown component navigation doesn't work *(expected: dropdown navigation should work)* > - Dropdown component element unselects the DT *(expected: the DT row should stay selected)* > - Dropdown component focus on input element when the new type selected *(expected: dropdown should stay focused)* -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3674) UX proposal for error reporting after test run

by Tao Zhu (Jira)

[ https://issues.jboss.org/browse/DROOLS-3674?page=com.atlassian.jira.plugi... ] Tao Zhu commented on DROOLS-3674: --------------------------------- [~gabriolo] could we use "hover" not "click" to show this popover? > UX proposal for error reporting after test run > ---------------------------------------------- > > Key: DROOLS-3674 > URL: https://issues.jboss.org/browse/DROOLS-3674 > Project: Drools > Issue Type: Task > Components: Scenario Simulation and Testing > Reporter: Daniele Zonca > Assignee: Tao Zhu > Priority: Major > Labels: ScenarioSimulation, UXTeam > Attachments: Error reporting after test run-different kinds.png, Error reporting after test run-different kinds2.png, Error reporting after test run-popup.png, Error reporting after test run-popup.png, Error reporting after test run.png > > > As user after a test run, I want see not only the cell that are not correct (red background) but also the reason. > For instance have the possibility to see the actual value that is different from the expected or the error message. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-628) Jaeger - Review and document usage of UMB

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-628?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy resolved SWSQE-628. ----------------------------------- Resolution: Done > Jaeger - Review and document usage of UMB > ----------------------------------------- > > Key: SWSQE-628 > URL: https://issues.jboss.org/browse/SWSQE-628 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matthew Mahoney > Assignee: Jeeva Kandasamy > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (SWSQE-628) Jaeger - Review and document usage of UMB

by Jeeva Kandasamy (Jira)

[ https://issues.jboss.org/browse/SWSQE-628?page=com.atlassian.jira.plugin.... ] Jeeva Kandasamy commented on SWSQE-628: --------------------------------------- Updated in https://docs.google.com/document/d/1mWDkz2GaDEzWdQrWM6Wdh68rxmqJKKy1ZVHbj... > Jaeger - Review and document usage of UMB > ----------------------------------------- > > Key: SWSQE-628 > URL: https://issues.jboss.org/browse/SWSQE-628 > Project: Kiali QE > Issue Type: Sub-task > Reporter: Matthew Mahoney > Assignee: Jeeva Kandasamy > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-3868) Upgrade antlr4-runtime version to 4.7.2

by Dominik Hanak (Jira)

Dominik Hanak created DROOLS-3868: ------------------------------------- Summary: Upgrade antlr4-runtime version to 4.7.2 Key: DROOLS-3868 URL: https://issues.jboss.org/browse/DROOLS-3868 Project: Drools Issue Type: Task Components: DMN Editor Affects Versions: 7.20.0.Final Reporter: Dominik Hanak Assignee: Dominik Hanak There is a new version of antlr4-runtime - 4.7.2. We use 4.5.3 in community. It would be nice to upgrade to version 4.7.2. NOTE: This is also needed for - https://issues.jboss.org/browse/JBPM-8195 I prepared a PR - https://github.com/kiegroup/droolsjbpm-build-bootstrap/pull/946 Running FDB shows that 9 tests started to fail. These are the failed tests: {code:java} org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[true] org.kie.dmn.core.DMNRuntimeTest.testInvalidVariableNames[false] org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterPercent org.kie.dmn.feel.parser.feel11.FEELParserTest.testVariableNameWithInvalidCharacterAt org.kie.dmn.validation.ValidatorTest.testVALIDATION org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_DefinitionsInput org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_FileInput org.kie.dmn.validation.ValidatorTypeRefTest.testTYPEREF_NOT_FEEL_NOT_DEF_ReaderInput {code} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11965) Upgrade WildFly HTTP Client to 1.0.15.Final

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11965?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11965: --------------------------------------- Assignee: Flavia Rainone (was: Stuart Douglas) > Upgrade WildFly HTTP Client to 1.0.15.Final > ------------------------------------------- > > Key: WFLY-11965 > URL: https://issues.jboss.org/browse/WFLY-11965 > Project: WildFly > Issue Type: Component Upgrade > Reporter: Ilia Vassilev > Assignee: Flavia Rainone > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4411) Introduce CapabilityServiceBuilder.setInstance(Service service) overriding method

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4411?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4411: ------------------------------------- Issue Type: Enhancement (was: Feature Request) I regard this as an Enhancement, as setInstance is already part of the API of CapabilityServiceBuilder. This just enhances the subinterface so callers doing call chaining can get back the subinterface when invoking it. This issue type distinction only matters because Feature Request issues normally go through the full proposal, etc cycle, which is not needed here. > Introduce CapabilityServiceBuilder.setInstance(Service service) overriding method > --------------------------------------------------------------------------------- > > Key: WFCORE-4411 > URL: https://issues.jboss.org/browse/WFCORE-4411 > Project: WildFly Core > Issue Type: Enhancement > Components: Server > Reporter: Richard Opalka > Assignee: Richard Opalka > Priority: Major > Fix For: 9.0.0.Beta3 > > -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFLY-11956: --------------------------------------- Component/s: REST Assignee: Alessio Soldano (was: Brian Stansberry) [~asoldano] I'm going to pass this one to you as the attached logging.txt from the reproducer application shows resteasy as being centrally involved in the two unexpected invocations, as it's JaxrsInjectionTarget that is triggering validation of the bean. org.jboss.weld.bean.ManagedBean.create calls JaxrsInjectionTarget.inject before it calls JaxrsInjectionTarget.postConstruct. It's the inject call that results in the "early" invocations of getHelloGreeting. [~guillaume.smet] [~manovotn] FYI. I don't know that what's being done here is necessarily wrong. An aside from whether JaxrsInjectionTarget.inject should be validating before the @PostConstruct is the first stack trace is a bit funky, where the JPA (Hibernate) PersistenceUtilHelper ends up invoking getHelloGreeting. > @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11956 > URL: https://issues.jboss.org/browse/WFLY-11956 > Project: WildFly > Issue Type: Bug > Components: Bean Validation, REST > Affects Versions: 16.0.0.Final > Reporter: Joerg Baesner > Assignee: Alessio Soldano > Priority: Major > Attachments: logging.txt, playground.zip > > > Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_: > {code} > @Path("/validated") > public interface ValidatedJaxRsInterface { > > @GET > @Valid > @Produces(MediaType.APPLICATION_JSON) > GreetingModel getHelloGreeting(); > } > {code} > will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed. > This can be reproduced with the attached reproducer application... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-11956) @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFLY-11956: ------------------------------------ Attachment: (was: logging.txt) > @PostConstruct on @ApplicationScoped bean called too late in case @Valid is annotated on a business method > ---------------------------------------------------------------------------------------------------------- > > Key: WFLY-11956 > URL: https://issues.jboss.org/browse/WFLY-11956 > Project: WildFly > Issue Type: Bug > Components: Bean Validation > Affects Versions: 16.0.0.Final > Reporter: Joerg Baesner > Assignee: Brian Stansberry > Priority: Major > Attachments: logging.txt, playground.zip > > > Having a bean class with {{@ApplicationScoped}}, which has a {{@PostConstruct}} and is implementing the following _Interface_: > {code} > @Path("/validated") > public interface ValidatedJaxRsInterface { > > @GET > @Valid > @Produces(MediaType.APPLICATION_JSON) > GreetingModel getHelloGreeting(); > } > {code} > will result in calling the {{getHelloGreeting}} method of the implementation class twice *_before_* the {{@PostConstruct}} is getting executed. > This can be reproduced with the attached reproducer application... -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

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 April 2019