February 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3241) [DMN Designer] Improve the Data Types support (7.3)

by Guilherme Carreiro (Jira)

[ https://issues.jboss.org/browse/DROOLS-3241?page=com.atlassian.jira.plugi... ] Guilherme Carreiro resolved DROOLS-3241. ---------------------------------------- Resolution: Done > [DMN Designer] Improve the Data Types support (7.3) > --------------------------------------------------- > > Key: DROOLS-3241 > URL: https://issues.jboss.org/browse/DROOLS-3241 > Project: Drools > Issue Type: Epic > Components: DMN Editor > Reporter: Guilherme Carreiro > Assignee: Guilherme Carreiro > Priority: Major > Labels: drools-tools > > As a practitioner, I want to be able to define Data Types in the UI, so that when the DMN engine evaluates a decision table input/output it will check if the type of the value matches the specified type. > Verification conditions: > Support added for the User to define data-types ({{ItemDefinition}}). > This may become a top-level task when I get to work on it; as the requirement is quite large and encompasses nested data-types (a whole new grid will be required); and definition of enums, constrains on values etc. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1745) The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration.

by Justin Cook (Jira)

[ https://issues.jboss.org/browse/ELY-1745?page=com.atlassian.jira.plugin.s... ] Justin Cook commented on ELY-1745: ---------------------------------- [~dlofthouse] Can you give me the steps to reproduce the problem? I tried running the Elytron web test with the mechanism configuration selector [1] stuff commented out and ran into an NPE [2] but it doesn't happen in the AvailableRealmsCallback, it happens before. [1] {noformat} ElytronAuthenticator elytronAuthenticator = ElytronAuthenticator.builder() .setSecurityDomain(securityDomain) //.setMechanismConfigurationSelector(MechanismConfigurationSelector.constantSelector( // MechanismConfiguration.builder() // .addMechanismRealm(MechanismRealmConfiguration.builder().setRealmName("Elytron Realm").build()) // .build())) .setFactory(httpServerMechanismFactory) .build(); {noformat} [2] {noformat} java.lang.NullPointerException at org.wildfly.security.auth.server.ServerAuthenticationContext$InactiveState.selectMechanismConfiguration(ServerAuthenticationContext.java:1427) at org.wildfly.security.auth.server.ServerAuthenticationContext$InactiveState.transition(ServerAuthenticationContext.java:1422) at org.wildfly.security.auth.server.ServerAuthenticationContext$InactiveState.getMechanismConfiguration(ServerAuthenticationContext.java:1401) at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handleOne(ServerAuthenticationContext.java:1036) at org.wildfly.security.auth.server.ServerAuthenticationContext$1.handle(ServerAuthenticationContext.java:839) at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$SecurityIdentityCallbackHandler.handle(SecurityIdentityServerMechanismFactory.java:120) at org.wildfly.security.http.impl.BasicAuthenticationMechanism.evaluateRequest(BasicAuthenticationMechanism.java:97) at org.wildfly.security.http.util.SecurityIdentityServerMechanismFactory$1.evaluateRequest(SecurityIdentityServerMechanismFactory.java:84) at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.authenticate(HttpAuthenticator.java:232) at org.wildfly.security.http.HttpAuthenticator$AuthenticationExchange.access$800(HttpAuthenticator.java:211) at org.wildfly.security.http.HttpAuthenticator.authenticate(HttpAuthenticator.java:95) at org.wildfly.elytron.web.jetty.server.ElytronAuthenticator.validateRequest(ElytronAuthenticator.java:95) at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:483) at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:132) at org.eclipse.jetty.server.Server.handle(Server.java:531) at org.eclipse.jetty.server.HttpChannel.handle(HttpChannel.java:352) at org.eclipse.jetty.server.HttpConnection.onFillable(HttpConnection.java:260) at org.eclipse.jetty.io.AbstractConnection$ReadCallback.succeeded(AbstractConnection.java:281) at org.eclipse.jetty.io.FillInterest.fillable(FillInterest.java:102) at org.eclipse.jetty.io.ChannelEndPoint$2.run(ChannelEndPoint.java:118) at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:762) at org.eclipse.jetty.util.thread.QueuedThreadPool$2.run(QueuedThreadPool.java:680) at java.base/java.lang.Thread.run(Thread.java:834) {noformat} > The AvailableRealmsCallback should not result in a NPE if there is no mechanism configuration. > ---------------------------------------------------------------------------------------------- > > Key: ELY-1745 > URL: https://issues.jboss.org/browse/ELY-1745 > Project: WildFly Elytron > Issue Type: Bug > Components: API / SPI > Reporter: Darran Lofthouse > Assignee: Justin Cook > Priority: Major > Fix For: 1.8.0.CR3 > > > The NPE is due to the following code: - > {noformat} > } else if (callback instanceof AvailableRealmsCallback) { > Collection<String> names = stateRef.get().getMechanismConfiguration().getMechanismRealmNames(); > if (log.isTraceEnabled()) { > log.tracef("Handling AvailableRealmsCallback: realms = [%s]", String.join(", ", names)); > } > if (! names.isEmpty()) { > ((AvailableRealmsCallback) callback).setRealmNames(names.toArray(new String[names.size()])); > } > handleOne(callbacks, idx + 1); > {noformat} > If mechanism configuration is mandatory this should report an appropriate error, if not it should fallback to specifying an empty list. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1813) Guided Decision Table Editor: Add support for sorting columns

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1813?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1813. ------------------------------------ Resolution: Won't Do > Guided Decision Table Editor: Add support for sorting columns > ------------------------------------------------------------- > > Key: DROOLS-1813 > URL: https://issues.jboss.org/browse/DROOLS-1813 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1812) [Guided Decision Table] Edit multiple cells at once

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1812?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1812. ------------------------------------ Resolution: Won't Do > [Guided Decision Table] Edit multiple cells at once > --------------------------------------------------- > > Key: DROOLS-1812 > URL: https://issues.jboss.org/browse/DROOLS-1812 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Labels: reported-by-qe > > The user of guided decision table editor is not able to edit values of multiple cells at once. > User is able to select multiple cells as belonging to same columns so belonging to different columns. For the case when the selected cells belong to the same column (the have the same data type) user should be able to edit all selected cells by one action. > Tried ways how to edit multiple cells: > * Select cells -> Menu -> Edit - there is appropriate menu item > * Select cells -> Right click to one of selected cells - invoked context menu only for one cell > * Select cells -> Double left click to one of selected cells - similar as above > * Select cells -> Hit key Enter - only the last selected is edited -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1810) [Guided Decision Table] Enumeration not loaded from multiple files

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1810?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1810. ------------------------------------ Resolution: Won't Do > [Guided Decision Table] Enumeration not loaded from multiple files > ------------------------------------------------------------------ > > Key: DROOLS-1810 > URL: https://issues.jboss.org/browse/DROOLS-1810 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.2.0.Final > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Minor > Attachments: Screenshot from 2017-09-04 18-46-06.png > > > User can define enumerations for pattern fields. The problem seems to be if enumerations for the same field are defined in multiple files. > # Open the mortgages project > # In the package mortgages.mortgages create enumeration like shown in the attachment > # Open the GDT Pricing loans > # Define new condition column like: $applicant : Applicant (creditRating == [literal value]) > # Append row into the table > # Try to select creditRating 'abcd' in the last row of the new column > -- 'abcd' will be missing -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1816) Guided Decision Table: for boolean values, it is not clear if the cell is not set or is set to false

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1816?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1816. ------------------------------------ Resolution: Won't Do > Guided Decision Table: for boolean values, it is not clear if the cell is not set or is set to false > ---------------------------------------------------------------------------------------------------- > > Key: DROOLS-1816 > URL: https://issues.jboss.org/browse/DROOLS-1816 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Zuzka Krejčová > Assignee: Guilherme Carreiro > Priority: Major > Labels: reported-by-qe > > A cell that represents a boolean field uses a simple checkbox to set the value to either true or false. Until the user first sets the value, the box is unchecked, but the value is not set. If the user checks and unchecks the box, the box looks just like at the beginning but the value is set to false. > If you want to determine if the cell value is not set yet or is set to false, you have to look into the source of the GDT. This is quite bothersome for larger tables. > Please consider some way of distinguishing these two different states in the guided dt editor. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1815) [Guided Decision Table] Non intuitive binding of fields without operators

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1815?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1815. ------------------------------------ Resolution: Won't Do > [Guided Decision Table] Non intuitive binding of fields without operators > ------------------------------------------------------------------------- > > Key: DROOLS-1815 > URL: https://issues.jboss.org/browse/DROOLS-1815 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Michael Anstis > Priority: Major > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > > There are situations when user wants to bind to variable field of a fact and he doesn't want to restrict the value of the field. Lets say that user wants to bind score of a player like this: > {code:java} > $p : Player( $s : score ) > {code} > This is completely possible with BRL Condition fragment. However if this rule is defined via Simple Condition column then it is a little bit non intuitive. > During Simple Condition definition user has to select Operator as *no operator*. But then in the table, to generate rule for this column there have to be filled some value in the corresponding cell, what is quite non intuitive. There should be just check box for cases, when we don't compare field with any value. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1817) [Guided Decision Table] Fields can not be bound in the wizard

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1817?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1817. ------------------------------------ Resolution: Won't Do > [Guided Decision Table] Fields can not be bound in the wizard > ------------------------------------------------------------- > > Key: DROOLS-1817 > URL: https://issues.jboss.org/browse/DROOLS-1817 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta5 > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Major > Labels: dtable_testday_preparation, qe-test-day, reported-by-qe > Attachments: Screenshot from 2017-01-04 14-56-18.png, Screenshot from 2017-01-04 14-56-35.png > > > In the Guided Decision Table editor, the user is able to bind column field to some name. This option is completely missing in the Guided Decision Table Wizard. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1827) [Guided Decision Table] Remove support for in-pattern eval

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1827?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1827. ------------------------------------ Resolution: Won't Do > [Guided Decision Table] Remove support for in-pattern eval > ---------------------------------------------------------- > > Key: DROOLS-1827 > URL: https://issues.jboss.org/browse/DROOLS-1827 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Reporter: Michael Anstis > Assignee: Michael Anstis > Priority: Major > > See https://issues.jboss.org/browse/GUVNOR-3432?focusedCommentId=13474867&pag... > {quote} > Also, please note that eval() inside patterns should not be used. The parser actually strips out all the eval()s inside patterns that it finds. Only top level evals are still useful. > {quote} > Support for "predicate" columns in the Guided Decision Table Editor need to be removed. Support in the UI and model-DRL conversion can be removed. We would also need to write a conversion routine converting predicates to BRL Condition Column {{RuleModel}} expressions. There may be a limitation to what the Expression Editor can support; so we'd need to fall back to Free From Lines. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1823) [Guided Decision Table] Preserve values during column definition change

by Michael Anstis (Jira)

[ https://issues.jboss.org/browse/DROOLS-1823?page=com.atlassian.jira.plugi... ] Michael Anstis resolved DROOLS-1823. ------------------------------------ Resolution: Won't Do > [Guided Decision Table] Preserve values during column definition change > ----------------------------------------------------------------------- > > Key: DROOLS-1823 > URL: https://issues.jboss.org/browse/DROOLS-1823 > Project: Drools > Issue Type: Enhancement > Components: Guided Decision Table Editor > Affects Versions: 7.0.0.Beta7 > Reporter: Jozef Marko > Assignee: Guilherme Carreiro > Priority: Minor > Labels: reported-by-qe > > There are cases when it would be worth to preserve cell values during column definition change. > For example if there is column like: *$p : Person (age == $value)* and it is changed to *$p : Person (name == $value)* where *age: Integer* and *name: String* then if there was cell value *10* it could change to *"10"*. -- This message was sent by Atlassian Jira (v7.12.1#712002)

5 years, 9 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 February 2019