April 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3934) [DMN Designer] Included Models - Boxed Expressions - Fetch information about imported Boxed Expressions in the DMNMarshaller

by Guilherme Gomes (Jira)

Guilherme Gomes created DROOLS-3934: --------------------------------------- Summary: [DMN Designer] Included Models - Boxed Expressions - Fetch information about imported Boxed Expressions in the DMNMarshaller Key: DROOLS-3934 URL: https://issues.jboss.org/browse/DROOLS-3934 Project: Drools Issue Type: Task Components: DMN Editor Reporter: Guilherme Gomes Assignee: Guilherme Gomes Currently, users are not able to see a boxed expression from an imported node. The DMNMarshaller must fetch information about external boxed expressions, and users must be able to see those boxed expressions in the DMN editor. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3831) [DMN Designer] Included Models - Fetch information about imported DRG Elements and Item Definitions in the DMNMarshaller

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3831?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3831: ------------------------------------ Summary: [DMN Designer] Included Models - Fetch information about imported DRG Elements and Item Definitions in the DMNMarshaller (was: [DMN Designer] Included Models - Add information about imported DRG Elements and Item Definitions in the DMNMarshaller) > [DMN Designer] Included Models - Fetch information about imported DRG Elements and Item Definitions in the DMNMarshaller > ------------------------------------------------------------------------------------------------------------------------ > > Key: DROOLS-3831 > URL: https://issues.jboss.org/browse/DROOLS-3831 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > The DMNMarshaller must fetch information about external DMN models (this information is extracted from the {{imports}} field from the diagram {{definitions}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3892) DMN (DEV): Add a nested row to a new Structured data type by default

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3892?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-3892: -------------------------------------- Sprint: 2019 Week 17-19 > DMN (DEV): Add a nested row to a new Structured data type by default > -------------------------------------------------------------------- > > Key: DROOLS-3892 > URL: https://issues.jboss.org/browse/DROOLS-3892 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Elizabeth Clayton > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > Attachments: Screen Shot 2019-04-03 at 4.15.11 PM.png > > > Usability enhancement request: Reduce the number of clicks / actions to add a nested element. > Solution description: > When the user creates a data type, of the type "Structured" a child row will get added to the list automatically. The child row will be in Edit mode by default. Design demo to illustrate. https://redhat.invisionapp.com/share/FERHG55ZAPH -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

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: -------------------------------- Attachment: project-dialogs.webm > [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: Michael Anstis > Priority: Major > Labels: drools-tools > Attachments: 2019-01-31 15.02.26.gif, project-dialogs.webm > > > 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)

5 years, 6 months

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 Christian Zambrano (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Christian Zambrano edited comment on WFLY-11956 at 4/23/19 9:39 AM: -------------------------------------------------------------------- > 1. As Christian has verified, it seems that getHelloGreeting() is getting called because A) it is a getter, and B) @Valid says that the returned GreetingModel should be validated, which means that getHelloGreeting() must be called. [~ron_sigal] I know you just explained this to Martin above but I still don't get it. Here is how I am interpreting what you are saying, The Valid annotation is on a method, which one would expect would be triggered on method invocation, but because it is on a method that starts with 'get'(JavaBeans standard), the Valid annotation seems to be interpreted as requesting field-level validation which results on the call to getHelloGreeting be called right after a object of the class that implements the interface ValidatedJaxRsInterface is instantiated to answer the rest call instead of waiting for the method to be called for the first time. Did I get that right? Your proposal of delaying the behavior described above until the PostConstruct is called, while better it can still lead to problems as the postConstruct may not have initialized everything is needed for the method to be called so having a way to turn this behavior off would be ideal for these cases. was (Author: christian.zambrano): > 1. As Christian has verified, it seems that getHelloGreeting() is getting called because A) it is a getter, and B) @Valid says that the returned GreetingModel should be validated, which means that getHelloGreeting() must be called. [~ron_sigal] I know you just explained this to Martin above but I still don't get it. Here is how I am interpreting what you are saying, The Valid annotation is on a method, which means it should be triggered on method invocation, but because it is on a method that starts with 'get'(JavaBeans standard), the Valid annotation seems to be interpreted as requesting field-level validation which results on the call to getHelloGreeting be called right after a object of the class that implements the interface ValidatedJaxRsInterface is instantiated to answer the rest call instead of waiting for the method to be called for the first time. Did I get that right? Your proposal of delaying the behavior described above until the PostConstruct is called, while better it can still lead to problems as the postConstruct may not have initialized everything is needed for the method to be called so having a way to turn this behavior off would be ideal for these cases. > @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: Ronald Sigal > 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)

5 years, 6 months

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 Christian Zambrano (Jira)

[ https://issues.jboss.org/browse/WFLY-11956?page=com.atlassian.jira.plugin... ] Christian Zambrano commented on WFLY-11956: ------------------------------------------- > 1. As Christian has verified, it seems that getHelloGreeting() is getting called because A) it is a getter, and B) @Valid says that the returned GreetingModel should be validated, which means that getHelloGreeting() must be called. [~ron_sigal] I know you just explained this to Martin above but I still don't get it. Here is how I am interpreting what you are saying, The Valid annotation is on a method, which means it should be triggered on method invocation, but because it is on a method that starts with 'get'(JavaBeans standard), the Valid annotation seems to be interpreted as requesting field-level validation which results on the call to getHelloGreeting be called right after a object of the class that implements the interface ValidatedJaxRsInterface is instantiated to answer the rest call instead of waiting for the method to be called for the first time. Did I get that right? Your proposal of delaying the behavior described above until the PostConstruct is called, while better it can still lead to problems as the postConstruct may not have initialized everything is needed for the method to be called so having a way to turn this behavior off would be ideal for these cases. > @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: Ronald Sigal > 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)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3831) [DMN Designer] Included Models - Add information about imported DRG Elements and Item Definitions in the DMNMarshaller

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3831?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3831: ------------------------------------ Summary: [DMN Designer] Included Models - Add information about imported DRG Elements and Item Definitions in the DMNMarshaller (was: [DMN Designer] Included Models - Add information about external DRG Elements and Item Definitions in the DMNMarshaller) > [DMN Designer] Included Models - Add information about imported DRG Elements and Item Definitions in the DMNMarshaller > ---------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3831 > URL: https://issues.jboss.org/browse/DROOLS-3831 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > The DMNMarshaller must fetch information about external DMN models (this information is extracted from the {{imports}} field from the diagram {{definitions}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3933) Test results coming from the backend are not i18n

by Toni Rikkola (Jira)

Toni Rikkola created DROOLS-3933: ------------------------------------ Summary: Test results coming from the backend are not i18n Key: DROOLS-3933 URL: https://issues.jboss.org/browse/DROOLS-3933 Project: Drools Issue Type: Feature Request Components: Scenario Simulation and Testing Reporter: Toni Rikkola Assignee: Daniele Zonca Some cultures are really strict about seeing the English language in the UI and then again not all people understand English. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3831) [DMN Designer] Included Models - Add information about external DRG Elements and Item Definitions in the DMNMarshaller

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3831?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3831: ------------------------------------ Summary: [DMN Designer] Included Models - Add information about external DRG Elements and Item Definitions in the DMNMarshaller (was: [DMN Designer] Included Models - Add information about external DRG Elements in the DMNMarshaller) > [DMN Designer] Included Models - Add information about external DRG Elements and Item Definitions in the DMNMarshaller > ---------------------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3831 > URL: https://issues.jboss.org/browse/DROOLS-3831 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > The DMNMarshaller must fetch information about external DMN models (this information is extracted from the {{imports}} field from the diagram {{definitions}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3831) [DMN Designer] Included Models - Add information about external DRG Elements in the DMNMarshaller

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3831?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3831: ------------------------------------ Summary: [DMN Designer] Included Models - Add information about external DRG Elements in the DMNMarshaller (was: [DMN Designer] Included Models - Add information about external DMN models in the DMNMarshaller) > [DMN Designer] Included Models - Add information about external DRG Elements in the DMNMarshaller > ------------------------------------------------------------------------------------------------- > > Key: DROOLS-3831 > URL: https://issues.jboss.org/browse/DROOLS-3831 > Project: Drools > Issue Type: Task > Components: DMN Editor > Reporter: Guilherme Gomes > Assignee: Guilherme Gomes > Priority: Major > Labels: drools-tools > > The DMNMarshaller must fetch information about external DMN models (this information is extracted from the {{imports}} field from the diagram {{definitions}}. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 6 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira April 2019