January 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3242) [Scenario Simulation] Update cell (double-)click interactions

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-3242?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-3242: ---------------------------------- Sprint: 2019 Week 05-07 > [Scenario Simulation] Update cell (double-)click interactions > -------------------------------------------------------------- > > Key: DROOLS-3242 > URL: https://issues.jboss.org/browse/DROOLS-3242 > Project: Drools > Issue Type: Feature Request > Components: Scenario Simulation and Testing > Affects Versions: 7.10.0.Final > Reporter: Ivo Bek > Assignee: Gabriele Cardosi > Priority: Major > Labels: ScenarioSimulation, UX, UXTeam > > Following from a discussion about https://issues.jboss.org/browse/DROOLS-2874 it was agreed that editing cells (header or body) in the grids should respond to single-click and not double-click. > h2. Manual Acceptance Test > - Not possible edit multiple cells by hold CTRL and click on multiple cells > - Click column/row leading cell discard edit dialog > - Edit can be discarded by escape > - Edit can be discarded by click to canvas > - Invoke edit of cell > - Save and reopen > - Undo redo of editation -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-2866) Docks used by editors are broken in embed enviroments

by Daniele Zonca (Jira)

[ https://issues.jboss.org/browse/DROOLS-2866?page=com.atlassian.jira.plugi... ] Daniele Zonca updated DROOLS-2866: ---------------------------------- Sprint: 2019 Week 05-07 > Docks used by editors are broken in embed enviroments > ----------------------------------------------------- > > Key: DROOLS-2866 > URL: https://issues.jboss.org/browse/DROOLS-2866 > Project: Drools > Issue Type: Bug > Components: DMN Editor, Stunner > Reporter: Toni Rikkola > Assignee: Toni Rikkola > Priority: Major > Labels: ScenarioSimulation, ScenarioSimulationTeam, drools-tools > > Any editor depending on the need of Docks needs a Perspective around it to have the Docks included. > This means the Appformer standalone editor perspective or any custom perspective that uses these screens does not show the Docks panel and the editor lacks editing features. > Areas hit by this issue: > * DMN Editor > * Data Modeller > * Scenario Simulation editor > * Case management editor > * BPMN Process editor > * Page authoring editor > * Form layout editor > * Manage section > Possible fixes: > * Add a dock for the editor > * Add a dock for appformer standalone perspective > Might be it is enough to add the dock for standalone perspective. This needs some investigation. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFWIP-102) SNI - hostname notation for sni-mapping element does not conform generic rules

by Jan Stourac (Jira)

[ https://issues.jboss.org/browse/WFWIP-102?page=com.atlassian.jira.plugin.... ] Jan Stourac commented on WFWIP-102: ----------------------------------- This is not issue anymore with new implementation as a property based attribute {{host-context-map}}. Dots don't have to be escaped anymore and asterisk can be used without preceding dot character. Although asterisk is required to be escaped now. Is it something that can be easily changed somehow [~dlofthouse]? What I am talking about is e.g.: {code} /subsystem=elytron/server-ssl-sni-context=serverSslSniCtx:write-attribute(name=host-context-map,value={www.example.com=exampleSslCtxName, "\\*.example.com"=asteriskExampleSslCtxName}) {code} Without asterisk being escaped, previous command still works, although during the reload operation following error occurrs: {code} 08:41:50,543 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) WFLYCTL0013: Operation ("add") failed - address: ([ ("subsystem" => "elytron"), ("server-ssl-sni-context" => "serverSslSniCtx") ]) - failure description: {"WFLYCTL0080: Failed services" => {"org.wildfly.security.ssl-context.serverSslSniCtx" => "Failed to start service Caused by: java.util.regex.PatternSyntaxException: Dangling meta character '*' near index 0 *.example.com ^"}} {code} If it's not feasible to change, let's just document it or check that it is properly documented. > SNI - hostname notation for sni-mapping element does not conform generic rules > ------------------------------------------------------------------------------ > > Key: WFWIP-102 > URL: https://issues.jboss.org/browse/WFWIP-102 > Project: WildFly WIP > Issue Type: Bug > Environment: Wildfly build with undertow and wildfly-core modules build from following sources: > * https://github.com/stuartwdouglas/undertow/tree/sni > * https://github.com/stuartwdouglas/wildfly-core/tree/sni > Reporter: Jan Stourac > Assignee: Darran Lofthouse > Priority: Major > > Way of configuration of {{sni-mapping}} element in {{server-ssl-sni-context}} is not nice from UX and also does not conform the way it is generally used. > With current implementation administrator has to use following notation: > {code} > .*\.example\.com > {code} > This is standard reg-exp notation and is not for easy reading. I think following notation is much better and also is commonly used for this cases: > {code} > *.example.com > {code} > In other words - simple asterisk is used to match any subdomain and dot in our case does not stand for 'any single character'. Note that is the way it was described in [analysis document|https://github.com/wildfly/wildfly-proposals/pull/67/files#diff-...]. > Truth is that with this change we loose some flexibility, e.g. administrator won't be able to configure following: > {code} > www\.exa.ple\.com > {code} > But I doubt this is a common use case. WDYT? -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-10937) Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se

by Suganya Rajeswaran (Jira)

[ https://issues.jboss.org/browse/WFLY-10937?page=com.atlassian.jira.plugin... ] Suganya Rajeswaran commented on WFLY-10937: ------------------------------------------- [~jamezp] Tried as u said... getting the same exception again. > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > ------------------------------------------------------------------------------- > > Key: WFLY-10937 > URL: https://issues.jboss.org/browse/WFLY-10937 > Project: WildFly > Issue Type: Bug > Components: Scripts > Reporter: Marek Kopecký > Assignee: Richard Opalka > Priority: Blocker > Labels: Java11, blocker-WF14, jdk11 > Fix For: 15.0.0.Beta1, 15.0.0.Final > > Attachments: appclient.conf.bat > > > Starting WFLY scripts with JDK 11 blows up with ModuleNotFoundException java.se > *Affected scripts* > * appclient > * jdr > * wsconsume > * wsprovide > *Example of logs* > {noformat} > [mkopecky@dhcp-10-40-4-197 bin]$ ./jdr.sh > org.jboss.modules.ModuleNotFoundException: java.se > at org.jboss.modules.Module.addPaths(Module.java:1266) > at org.jboss.modules.Module.link(Module.java:1622) > at org.jboss.modules.Module.relinkIfNecessary(Module.java:1650) > at org.jboss.modules.ModuleLoader.loadModule(ModuleLoader.java:296) > at org.jboss.modules.Main.main(Main.java:437) > [mkopecky@dhcp-10-40-4-197 bin]$ > {noformat} -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3455: --------------------------------------- Yes, everywhere where a duration is accepted, we should use the same "form". > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3546) DMN fix FEEL context entry when key is a string literal

by Edson Tirelli (Jira)

[ https://issues.jboss.org/browse/DROOLS-3546?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-3546: --------------------------------------- [~tari_manga] what I mean is that you are doing the correct thing here to be compliant with the spec, but I believe the RTF didn't think this through properly... if someone uses characters in the string that are not valid in a FEEL name, that key becomes inaccessible.... So close this ticket with your fix, but we should raise this on the RTF. > DMN fix FEEL context entry when key is a string literal > ------------------------------------------------------- > > Key: DROOLS-3546 > URL: https://issues.jboss.org/browse/DROOLS-3546 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > Priority: Major > Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot-4.png, screenshot-5.png > > > Ref FEEL grammar rule 61 -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton commented on DROOLS-3455: ------------------------------------- [~tirelli][~karreiro] I posted the revised Range mockup. Is this change is needed for enumeration as well? > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3455: -------------------------------- Attachment: enumeration.png > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3455: -------------------------------- Attachment: (was: enumeration.png) > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-3455) Data type constraints: Year/Mos Duration

by Liz Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-3455?page=com.atlassian.jira.plugi... ] Liz Clayton updated DROOLS-3455: -------------------------------- Attachment: range-redo.png > Data type constraints: Year/Mos Duration > ---------------------------------------- > > Key: DROOLS-3455 > URL: https://issues.jboss.org/browse/DROOLS-3455 > Project: Drools > Issue Type: Story > Components: DMN Editor > Reporter: Liz Clayton > Assignee: Liz Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: enumeration.png, expression.png, range-redo.png, range.png > > > Background > Persona: Business analyst or Rules practitioner > Use Cases: > * From the DMN canvas view - as a user I want to define data type restrictions (one-off instances) from a decision table . > * From the Data Types tab - as a user I want the ability to define constraints for the following types: Year/Mos Duration (Expression, Enumeration, and Range.) > Functional considerations/ pre conditions: > * Consider interaction in light of Property panel and consistency. > * Underscore the notion of one-off constraints. > Verification conditions: > * Scrum team and PO review. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 3 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 January 2019