October 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4619?page=com.atlassian.jira.plugi... ] Elizabeth Clayton commented on DROOLS-4619: ------------------------------------------- [~porcelli] [~manstis] [~karreiro] I've took a first pass at this and have posted 2 alternatives, but both include the following changes: * Added a table icon to the cells where decision logic is the selection option. * Increased the size of the initial grid. * Changed the hint text to "Select decision logic." * Added a tooltip. Version A) All of the above, and otherwise no change to the current behavior. !icon-new.png|thumbnail! !icon-only.png|thumbnail! Version B) All of the above, but uses a dropdown selector instead of a pop-over. !dropdown-new.png|thumbnail! !mock1.png|thumbnail! > Hard to figure out how to select what type of expression the DMN decision will be > --------------------------------------------------------------------------------- > > Key: DROOLS-4619 > URL: https://issues.jboss.org/browse/DROOLS-4619 > Project: Drools > Issue Type: Enhancement > Reporter: Alexandre Bakos > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-10-08 at 4.42.38 PM.png, dropdown-new.png, icon-new.png, icon-only.png, mock1.png > > > I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table. > I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression. > A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4619?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4619: -------------------------------------- Attachment: icon-new.png > Hard to figure out how to select what type of expression the DMN decision will be > --------------------------------------------------------------------------------- > > Key: DROOLS-4619 > URL: https://issues.jboss.org/browse/DROOLS-4619 > Project: Drools > Issue Type: Enhancement > Reporter: Alexandre Bakos > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-10-08 at 4.42.38 PM.png, icon-new.png, icon-only.png > > > I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table. > I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression. > A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4619) Hard to figure out how to select what type of expression the DMN decision will be

by Elizabeth Clayton (Jira)

[ https://issues.jboss.org/browse/DROOLS-4619?page=com.atlassian.jira.plugi... ] Elizabeth Clayton updated DROOLS-4619: -------------------------------------- Attachment: icon-only.png > Hard to figure out how to select what type of expression the DMN decision will be > --------------------------------------------------------------------------------- > > Key: DROOLS-4619 > URL: https://issues.jboss.org/browse/DROOLS-4619 > Project: Drools > Issue Type: Enhancement > Reporter: Alexandre Bakos > Assignee: Elizabeth Clayton > Priority: Major > Labels: UX, UXTeam, drools-tools > Attachments: Screen Shot 2019-10-08 at 4.42.38 PM.png, icon-new.png, icon-only.png > > > I had a hard time to figure out that I had to click the cell to select what type of expression I'd like, that in my case was a decision table. > I right-clicked, I double-clicked the "Decision-1" header and took me a while to just click the cell that says: Select expression. > A very quick win for a very short time would change the message to something like: "click here to select expression"... but likely that a better interaction is needed to replace the current empty cell. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12655) Exception with web.xml url-pattern

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12655?page=com.atlassian.jira.plugin... ] James Perkins commented on WFLY-12655: -------------------------------------- I would say it's like the same issue. The {{/js/\*}} would fail on any of the {{/jsp}} ones. > Exception with web.xml url-pattern > ---------------------------------- > > Key: WFLY-12655 > URL: https://issues.jboss.org/browse/WFLY-12655 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 18.0.0.Final > Reporter: Frank Heldt > Assignee: Flavia Rainone > Priority: Blocker > Fix For: 19.0.0.Beta1 > > > Defining and securing 2 folders in a war with similar names given this Exception on deployment: > {code} > 12:38:37,994 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."java-web-project.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-web-project.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service > at org.jboss.as.security@18.0.0.Final//org.jboss.as.security.service.JaccService.start(JaccService.java:107) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalArgumentException: Invalid prefix pattern in URLPatternList > at javax.security.jacc.api@2.0.0.Final//javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:308) > at javax.security.jacc.api(a)2.0.0.Final//javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79) > at javax.security.jacc.api(a)2.0.0.Final//javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160) > at org.wildfly.extension.undertow@18.0.0.Final//org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:303) > at org.wildfly.extension.undertow@18.0.0.Final//org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64) > at org.jboss.as.security@18.0.0.Final//org.jboss.as.security.service.JaccService.start(JaccService.java:86) > ... 8 more > {code} > This is the corresponding part of the web.xml: > {code} > <security-constraint> > <web-resource-collection> > <web-resource-name>Area</web-resource-name> > <url-pattern>/area/*</url-pattern> > </web-resource-collection> > <auth-constraint> > <role-name>role1</role-name> > <role-name>role2</role-name> > </auth-constraint> > <user-data-constraint> > <transport-guarantee>CONFIDENTIAL</transport-guarantee> > </user-data-constraint> > </security-constraint> > <security-constraint> > <web-resource-collection> > <web-resource-name>Area 51</web-resource-name> > <url-pattern>/area51/*</url-pattern> > </web-resource-collection> > <auth-constraint> > <role-name>role1</role-name> > </auth-constraint> > <user-data-constraint> > <transport-guarantee>CONFIDENTIAL</transport-guarantee> > </user-data-constraint> > </security-constraint> > {code} > Looks like this only happens when the url-pattern starts with the same characters (eg /area/* and /area51/*). > The same war under WildFly 17.0.1 works as expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12655) Exception with web.xml url-pattern

by Petri Tuomaala (Jira)

[ https://issues.jboss.org/browse/WFLY-12655?page=com.atlassian.jira.plugin... ] Petri Tuomaala commented on WFLY-12655: --------------------------------------- Not sure if this is related. We get little different exception than from the bug description. Our exception is: WFLYSEC0012: Unable to start the JaccService service Caused by: java.lang.IllegalArgumentException: Invalid exact pattern in URLPatternList. Same config works on WLF17. Our security constraint is like this: {code:xml} <security-constraint> <web-resource-collection> <web-resource-name>All</web-resource-name> <url-pattern>/*</url-pattern> </web-resource-collection> <auth-constraint> <role-name>BASIC_ROLE</role-name> </auth-constraint> </security-constraint> <security-constraint> <web-resource-collection> <web-resource-name>Resources and login</web-resource-name> <url-pattern>/images/*</url-pattern> <url-pattern>/fonts/*</url-pattern> <url-pattern>/css/*</url-pattern> <url-pattern>/js/*</url-pattern> <url-pattern>/v/*</url-pattern> <url-pattern>*.js</url-pattern> <url-pattern>*.css</url-pattern> <url-pattern>/jsp/substitute/SMS/smsResponse.jsp</url-pattern> <url-pattern>/jsp/forgot_password.faces</url-pattern> <url-pattern>/jsp/forgot_password_sent.faces</url-pattern> <url-pattern>/jsp/create_password.faces</url-pattern> <url-pattern>/jsp/recruitment/direct.faces</url-pattern> <url-pattern>/javax.faces.resource/oamSubmit.js.faces</url-pattern> <http-method>GET</http-method> <http-method>POST</http-method> <http-method>HEAD</http-method> </web-resource-collection> </security-constraint> <security-constraint> <web-resource-collection> <web-resource-name>Public services</web-resource-name> <url-pattern>/services/*</url-pattern> <http-method>GET</http-method> <http-method>HEAD</http-method> <http-method>POST</http-method> </web-resource-collection> </security-constraint> {code} > Exception with web.xml url-pattern > ---------------------------------- > > Key: WFLY-12655 > URL: https://issues.jboss.org/browse/WFLY-12655 > Project: WildFly > Issue Type: Bug > Components: Web (Undertow) > Affects Versions: 18.0.0.Final > Reporter: Frank Heldt > Assignee: Flavia Rainone > Priority: Blocker > Fix For: 19.0.0.Beta1 > > > Defining and securing 2 folders in a war with similar names given this Exception on deployment: > {code} > 12:38:37,994 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-3) MSC000001: Failed to start service jboss.deployment.unit."java-web-project.war".jboss.security.jacc: org.jboss.msc.service.StartException in service jboss.deployment.unit."java-web-project.war".jboss.security.jacc: WFLYSEC0012: Unable to start the JaccService service > at org.jboss.as.security@18.0.0.Final//org.jboss.as.security.service.JaccService.start(JaccService.java:107) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.startService(ServiceControllerImpl.java:1739) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$StartTask.execute(ServiceControllerImpl.java:1701) > at org.jboss.msc@1.4.11.Final//org.jboss.msc.service.ServiceControllerImpl$ControllerTask.run(ServiceControllerImpl.java:1559) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1982) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1486) > at org.jboss.threads@2.3.3.Final//org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1377) > at java.base/java.lang.Thread.run(Thread.java:834) > Caused by: java.lang.IllegalArgumentException: Invalid prefix pattern in URLPatternList > at javax.security.jacc.api@2.0.0.Final//javax.security.jacc.URLPatternSpec.setURLPatternArray(URLPatternSpec.java:308) > at javax.security.jacc.api(a)2.0.0.Final//javax.security.jacc.URLPatternSpec.<init>(URLPatternSpec.java:79) > at javax.security.jacc.api(a)2.0.0.Final//javax.security.jacc.WebResourcePermission.<init>(WebResourcePermission.java:160) > at org.wildfly.extension.undertow@18.0.0.Final//org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:303) > at org.wildfly.extension.undertow@18.0.0.Final//org.wildfly.extension.undertow.security.jacc.WarJACCService.createPermissions(WarJACCService.java:64) > at org.jboss.as.security@18.0.0.Final//org.jboss.as.security.service.JaccService.start(JaccService.java:86) > ... 8 more > {code} > This is the corresponding part of the web.xml: > {code} > <security-constraint> > <web-resource-collection> > <web-resource-name>Area</web-resource-name> > <url-pattern>/area/*</url-pattern> > </web-resource-collection> > <auth-constraint> > <role-name>role1</role-name> > <role-name>role2</role-name> > </auth-constraint> > <user-data-constraint> > <transport-guarantee>CONFIDENTIAL</transport-guarantee> > </user-data-constraint> > </security-constraint> > <security-constraint> > <web-resource-collection> > <web-resource-name>Area 51</web-resource-name> > <url-pattern>/area51/*</url-pattern> > </web-resource-collection> > <auth-constraint> > <role-name>role1</role-name> > </auth-constraint> > <user-data-constraint> > <transport-guarantee>CONFIDENTIAL</transport-guarantee> > </user-data-constraint> > </security-constraint> > {code} > Looks like this only happens when the url-pattern starts with the same characters (eg /area/* and /area51/*). > The same war under WildFly 17.0.1 works as expected. -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1723) Separate auth client parsing from the API.

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1723?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1723: ---------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Separate auth client parsing from the API. > ------------------------------------------ > > Key: ELY-1723 > URL: https://issues.jboss.org/browse/ELY-1723 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 1.10.4.CR1, 2.0.0.Alpha6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1722) Remove 'wildfly-elytron-x500-deprecated'

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1722?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1722: ---------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Remove 'wildfly-elytron-x500-deprecated' > ---------------------------------------- > > Key: ELY-1722 > URL: https://issues.jboss.org/browse/ELY-1722 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 2.0.0.Alpha6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1720) Remove 'wildfly-elytron-sasl-deprecated'

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1720?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1720: ---------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Remove 'wildfly-elytron-sasl-deprecated' > ---------------------------------------- > > Key: ELY-1720 > URL: https://issues.jboss.org/browse/ELY-1720 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 2.0.0.Alpha6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1718) Remove 'wildfly-elytron-http-deprecated'

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1718?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1718: ---------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Remove 'wildfly-elytron-http-deprecated' > ---------------------------------------- > > Key: ELY-1718 > URL: https://issues.jboss.org/browse/ELY-1718 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 2.0.0.Alpha6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ELY-1717) Remove 'wildfly-elytron-credential-source-deprecated'

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/ELY-1717?page=com.atlassian.jira.plugin.s... ] Farah Juma updated ELY-1717: ---------------------------- Fix Version/s: 2.0.0.Alpha6 (was: 2.0.0.Alpha5) > Remove 'wildfly-elytron-credential-source-deprecated' > ----------------------------------------------------- > > Key: ELY-1717 > URL: https://issues.jboss.org/browse/ELY-1717 > Project: WildFly Elytron > Issue Type: Task > Reporter: Darran Lofthouse > Assignee: Ashley Abdel-Sayed > Priority: Blocker > Fix For: 2.0.0.Alpha6 > > -- This message was sent by Atlassian Jira (v7.13.8#713008)

6 years, 9 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 October 2019