June 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-3761) [DMN Designer] Data Types - Constraints - Enumeration constraint entry on edit mode - Fix buttons behavior

by Guilherme Gomes (Jira)

[ https://issues.jboss.org/browse/DROOLS-3761?page=com.atlassian.jira.plugi... ] Guilherme Gomes updated DROOLS-3761: ------------------------------------ Summary: [DMN Designer] Data Types - Constraints - Enumeration constraint entry on edit mode - Fix buttons behavior (was: [DMN Designer] Enumeration constraint entry edit mode) > [DMN Designer] Data Types - Constraints - Enumeration constraint entry on edit mode - Fix buttons behavior > ---------------------------------------------------------------------------------------------------------- > > Key: DROOLS-3761 > URL: https://issues.jboss.org/browse/DROOLS-3761 > Project: Drools > Issue Type: Bug > Components: DMN Editor > Affects Versions: 7.19.0.Final > Reporter: Jozef Marko > Assignee: Daniel José dos Santos > Priority: Minor > Labels: drools-tools > Attachments: constraint_unsaved.png, focus_lost.webm, lost_focus_data_types.webm > > > The attached video shows the user interaction with enumeration constraint component. We can see if user fill valid values and clicks somewhere outside of the entry in edit mode, the values are lost. The only way how to save values is to click the *check* button. User should not lost filled in values if he clicks outside of input fields. > Please compare the same behavior with data types list view component. It means [^focus_lost.webm] vs [^lost_focus_data_types.webm] . -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4521) add-user script fails when there is no domain configuration

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4521?page=com.atlassian.jira.plugi... ] Brian Stansberry reassigned WFCORE-4521: ---------------------------------------- Assignee: Brian Stansberry (was: Jean Francois Denise) > add-user script fails when there is no domain configuration > ----------------------------------------------------------- > > Key: WFCORE-4521 > URL: https://issues.jboss.org/browse/WFCORE-4521 > Project: WildFly Core > Issue Type: Bug > Components: Management, Scripts > Affects Versions: 9.0.1.Final > Environment: OS Darwin Kernel Version 17.7.0 > Java 1.8.0_192-ea > WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) > Reporter: Rafael Soares > Assignee: Brian Stansberry > Priority: Blocker > > When you have a wildfly installation with no domain configuration directory (WILDFLY_HOME/domain) the {{bin/add-user.sh}} fails because it expects both (standalone and domain) configs to exists in order to update the properties file... > It seems this behavior is fixed in the code implementation at [org.jboss.as.domain.management.security.adduser.AddUser.java|https://gith...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12085) java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties

by James Perkins (Jira)

[ https://issues.jboss.org/browse/WFLY-12085?page=com.atlassian.jira.plugin... ] James Perkins updated WFLY-12085: --------------------------------- Workaround Description: While not ideal you can filter out the message since it's a warning and doesn't cause any real issues. {code} /subsystem=logging/logger=org.apache.activemq.artemis.core.server:add(filter-spec=not(match("AMQ222277.*"))) {code} was:None > java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties > ------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: WFLY-12085 > URL: https://issues.jboss.org/browse/WFLY-12085 > Project: WildFly > Issue Type: Bug > Components: JMS > Affects Versions: 17.0.0.Alpha1, 17.0.0.Final > Environment: Red Hat JBoss Enterprise Application Platform > 7.2.1 > Microsoft Windows 10 > Reporter: Emmanuel Hugonnet > Assignee: Emmanuel Hugonnet > Priority: Major > > There seems to be a regression in JBoss EAP 7.2.1 patch. After applying it the following exception can be seen in the server log file during the startup: > {noformat} > 2019-05-13 11:45:11,419 WARN [org.apache.activemq.artemis.core.server] (ServerService Thread Pool -- 78) AMQ222277: Problem initializing automatic logging configuration reload for file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties: java.net.URISyntaxException: Illegal character in opaque part at index 7: file:C:\Java\jboss\jboss-as\standalone\configuration/logging.properties > at java.net.URI$Parser.fail(URI.java:2848) > at java.net.URI$Parser.checkChars(URI.java:3021) > at java.net.URI$Parser.parse(URI.java:3058) > at java.net.URI.<init>(URI.java:588) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.initialisePart1(ActiveMQServerImpl.java:2369) > at org.apache.activemq.artemis.core.server.impl.LiveOnlyActivation.run(LiveOnlyActivation.java:64) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.internalStart(ActiveMQServerImpl.java:544) > at org.apache.activemq.artemis.core.server.impl.ActiveMQServerImpl.start(ActiveMQServerImpl.java:481) > at org.apache.activemq.artemis.jms.server.impl.JMSServerManagerImpl.start(JMSServerManagerImpl.java:376) > at org.wildfly.extension.messaging.activemq.jms.JMSService.doStart(JMSService.java:206) > at org.wildfly.extension.messaging.activemq.jms.JMSService.access$000(JMSService.java:65) > at org.wildfly.extension.messaging.activemq.jms.JMSService$1.run(JMSService.java:100) > at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > at java.util.concurrent.FutureTask.run(FutureTask.java:266) > at org.jboss.threads.ContextClassLoaderSavingRunnable.run(ContextClassLoaderSavingRunnable.java:35) > at org.jboss.threads.EnhancedQueueExecutor.safeRun(EnhancedQueueExecutor.java:1985) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.doRunTask(EnhancedQueueExecutor.java:1487) > at org.jboss.threads.EnhancedQueueExecutor$ThreadBody.run(EnhancedQueueExecutor.java:1349) > at java.lang.Thread.run(Thread.java:748) > at org.jboss.threads.JBossThread.run(JBossThread.java:485) > {noformat} > This issue only affects Microsoft Windows platform. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4522) The add-user.sh script fails if $WILDFLY_HOME/domain is missing

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4522?page=com.atlassian.jira.plugi... ] Brian Stansberry resolved WFCORE-4522. -------------------------------------- Resolution: Duplicate Issue Duplicates WFCORE-4521 > The add-user.sh script fails if $WILDFLY_HOME/domain is missing > --------------------------------------------------------------- > > Key: WFCORE-4522 > URL: https://issues.jboss.org/browse/WFCORE-4522 > Project: WildFly Core > Issue Type: Bug > Components: Management, Security > Affects Versions: 9.0.1.Final > Reporter: Brian Stansberry > Assignee: Jeff Mesnil > Priority: Critical > > If the $WILDFLY_HOME/domain is missing (which will often be the case with a Galleon-provisioned server, using add-user.sh fails: > {code}$ bin/add-user.sh > What type of user do you wish to add? > a) Management User (mgmt-users.properties) > b) Application User (application-users.properties) > (a): a > * Error * > WFLYDM0106: File permissions problems found while attempting to update /home/bes/dev/wildfly/wildfly-core/build/target/wildfly-core-9.0.1.Final/domain/configuration/mgmt-users.properties file. > {code} > The problem is PropertyFileFinder is invoking the validatePermissions check on files that don't exist, and those checks fail not because of missing perms but because you can't read or execute non-existing files. The validatePermissions checks are called from findFiles, which is already dealing with non-existing files (i.e. not adding them to the foundFiles list and returning false if no files exist) so I don't see a reason to validate non-existing files. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4521) add-user script fails when there is no domain configuration

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4521?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-4521: ------------------------------------------ Using add-user.sh fails: {code}$ bin/add-user.sh What type of user do you wish to add? a) Management User (mgmt-users.properties) b) Application User (application-users.properties) (a): a * Error * WFLYDM0106: File permissions problems found while attempting to update /home/bes/dev/wildfly/wildfly-core/build/target/wildfly-core-9.0.1.Final/domain/configuration/mgmt-users.properties file. {code} The problem is PropertyFileFinder is invoking the validatePermissions check on files that don't exist, and those checks fail not because of missing perms but because you can't read or execute non-existing files. The validatePermissions checks are called from findFiles, which is already dealing with non-existing files (i.e. not adding them to the foundFiles list and returning false if no files exist) so I don't see a reason to validate non-existing files. > add-user script fails when there is no domain configuration > ----------------------------------------------------------- > > Key: WFCORE-4521 > URL: https://issues.jboss.org/browse/WFCORE-4521 > Project: WildFly Core > Issue Type: Bug > Components: CLI, Management, Scripts > Affects Versions: 9.0.1.Final > Environment: OS Darwin Kernel Version 17.7.0 > Java 1.8.0_192-ea > WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) > Reporter: Rafael Soares > Assignee: Jean Francois Denise > Priority: Major > > When you have a wildfly installation with no domain configuration directory (WILDFLY_HOME/domain) the {{bin/add-user.sh}} fails because it expects both (standalone and domain) configs to exists in order to update the properties file... > It seems this behavior is fixed in the code implementation at [org.jboss.as.domain.management.security.adduser.AddUser.java|https://gith...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4521) add-user script fails when there is no domain configuration

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4521?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4521: ------------------------------------- Component/s: (was: CLI) > add-user script fails when there is no domain configuration > ----------------------------------------------------------- > > Key: WFCORE-4521 > URL: https://issues.jboss.org/browse/WFCORE-4521 > Project: WildFly Core > Issue Type: Bug > Components: Management, Scripts > Affects Versions: 9.0.1.Final > Environment: OS Darwin Kernel Version 17.7.0 > Java 1.8.0_192-ea > WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) > Reporter: Rafael Soares > Assignee: Jean Francois Denise > Priority: Major > > When you have a wildfly installation with no domain configuration directory (WILDFLY_HOME/domain) the {{bin/add-user.sh}} fails because it expects both (standalone and domain) configs to exists in order to update the properties file... > It seems this behavior is fixed in the code implementation at [org.jboss.as.domain.management.security.adduser.AddUser.java|https://gith...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4521) add-user script fails when there is no domain configuration

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4521?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4521: ------------------------------------- Priority: Blocker (was: Major) > add-user script fails when there is no domain configuration > ----------------------------------------------------------- > > Key: WFCORE-4521 > URL: https://issues.jboss.org/browse/WFCORE-4521 > Project: WildFly Core > Issue Type: Bug > Components: Management, Scripts > Affects Versions: 9.0.1.Final > Environment: OS Darwin Kernel Version 17.7.0 > Java 1.8.0_192-ea > WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) > Reporter: Rafael Soares > Assignee: Jean Francois Denise > Priority: Blocker > > When you have a wildfly installation with no domain configuration directory (WILDFLY_HOME/domain) the {{bin/add-user.sh}} fails because it expects both (standalone and domain) configs to exists in order to update the properties file... > It seems this behavior is fixed in the code implementation at [org.jboss.as.domain.management.security.adduser.AddUser.java|https://gith...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4522) The add-user.sh script fails if $WILDFLY_HOME/domain is missing

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4522: ---------------------------------------- Summary: The add-user.sh script fails if $WILDFLY_HOME/domain is missing Key: WFCORE-4522 URL: https://issues.jboss.org/browse/WFCORE-4522 Project: WildFly Core Issue Type: Bug Components: Management, Security Affects Versions: 9.0.1.Final Reporter: Brian Stansberry Assignee: Jeff Mesnil If the $WILDFLY_HOME/domain is missing (which will often be the case with a Galleon-provisioned server, using add-user.sh fails: {code}$ bin/add-user.sh What type of user do you wish to add? a) Management User (mgmt-users.properties) b) Application User (application-users.properties) (a): a * Error * WFLYDM0106: File permissions problems found while attempting to update /home/bes/dev/wildfly/wildfly-core/build/target/wildfly-core-9.0.1.Final/domain/configuration/mgmt-users.properties file. {code} The problem is PropertyFileFinder is invoking the validatePermissions check on files that don't exist, and those checks fail not because of missing perms but because you can't read or execute non-existing files. The validatePermissions checks are called from findFiles, which is already dealing with non-existing files (i.e. not adding them to the foundFiles list and returning false if no files exist) so I don't see a reason to validate non-existing files. -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-4521) add-user script fails when there is no domain configuration

by Rafael Soares (Jira)

Rafael Soares created WFCORE-4521: ------------------------------------- Summary: add-user script fails when there is no domain configuration Key: WFCORE-4521 URL: https://issues.jboss.org/browse/WFCORE-4521 Project: WildFly Core Issue Type: Bug Components: CLI, Management, Scripts Affects Versions: 9.0.1.Final Environment: OS Darwin Kernel Version 17.7.0 Java 1.8.0_192-ea WildFly Full 17.0.0.Final (WildFly Core 9.0.1.Final) Reporter: Rafael Soares Assignee: Jean Francois Denise When you have a wildfly installation with no domain configuration directory (WILDFLY_HOME/domain) the {{bin/add-user.sh}} fails because it expects both (standalone and domain) configs to exists in order to update the properties file... It seems this behavior is fixed in the code implementation at [org.jboss.as.domain.management.security.adduser.AddUser.java|https://gith...] -- This message was sent by Atlassian Jira (v7.12.1#712002)

7 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-12187) Add documentation and test updates for TLS 1.3 support

by Farah Juma (Jira)

[ https://issues.jboss.org/browse/WFLY-12187?page=com.atlassian.jira.plugin... ] Farah Juma updated WFLY-12187: ------------------------------ Summary: Add documentation and test updates for TLS 1.3 support (was: Add documentation for TLS 1.3 support) > Add documentation and test updates for TLS 1.3 support > ------------------------------------------------------ > > Key: WFLY-12187 > URL: https://issues.jboss.org/browse/WFLY-12187 > Project: WildFly > Issue Type: Feature Request > Components: Security > Reporter: Farah Juma > Assignee: Farah Juma > Priority: Major > Labels: affects-model, eap-7.2.0-deferred > Fix For: 10.0.0.Beta1 > > > It presently appears as though TLS 1.3 support could be available from Java 11. -- 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 June 2019