October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-1672) "not" in variable name doesn't work

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1672?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1672: ---------------------------------- Fix Version/s: (was: 7.4.0.Final) > "not" in variable name doesn't work > ----------------------------------- > > Key: DROOLS-1672 > URL: https://issues.jboss.org/browse/DROOLS-1672 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Labels: reported-by-qe > > When trying this test case: > {code}{ is not exactly 18 : != 18, bob is not exactly 18 : is not exactly 18(16) }.bob is not exactly 18"{code} > the parser fails like this [1] > [1] https://gist.github.com/baldimir/7c13b9c76087d44f95802ded8b72877f > Will provide a PR with a reproducer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Edson Tirelli updated DROOLS-1663: ---------------------------------- Fix Version/s: (was: 7.4.0.Final) > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1663) Kie DMN doesn't support IMPORT decisions between DMN files

by Edson Tirelli (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Edson Tirelli commented on DROOLS-1663: --------------------------------------- I looked into this a bit more and the DMN import is broken as defined in the spec version 1.1. This is being fixed for 1.2, so we will not support it until 1.2 is supported. > Kie DMN doesn't support IMPORT decisions between DMN files > ---------------------------------------------------------- > > Key: DROOLS-1663 > URL: https://issues.jboss.org/browse/DROOLS-1663 > Project: Drools > Issue Type: Enhancement > Components: dmn engine > Reporter: Stylianos Koussouris > Assignee: Edson Tirelli > Fix For: 7.4.0.Final > > Attachments: IMG_2197.jpg, IMG_2198.jpg, IMG_2199.jpg > > > DMN Spec 1.1 > Page 40. > import: Import [*] This attribute is used to import externally defined elements and > make them available for use by elements in this Definitions. > Section 6.3.3 Import metamodel > The aim here is to be able to import one Decision defined in a separate DMN into another where it is used as a supporting decision and is referenced (RequiredDecision) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3323) Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper

by Ilia Vassilev (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3323?page=com.atlassian.jira.plugi... ] Ilia Vassilev reassigned WFCORE-3323: ------------------------------------- Assignee: Ilia Vassilev (was: Darran Lofthouse) > Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper > --------------------------------------------------------------------------------------- > > Key: WFCORE-3323 > URL: https://issues.jboss.org/browse/WFCORE-3323 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.3.Final > Reporter: Ondrej Lukas > Assignee: Ilia Vassilev > Priority: Minor > > As part of fix JBEAP-12933 there was added attribute {{mapping-mode="first"}} into "default-permission-mapper" {{simple-permission-mapper}} in default configuration. Value {{first}} is default value of {{simple-permission-mapper.mapping-mode}} which means that this attribute disappears after first change in server configuration. It can be confusing since Elytron subsystem configuration in XML is changed even if there was no request for changing that configuration. Attribute {{mapping-mode="first"}} should be removed from default configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9407) Upgrade Artemis 2.3.0

by Jeff Mesnil (JIRA)

Jeff Mesnil created WFLY-9407: --------------------------------- Summary: Upgrade Artemis 2.3.0 Key: WFLY-9407 URL: https://issues.jboss.org/browse/WFLY-9407 Project: WildFly Issue Type: Component Upgrade Components: JMS Reporter: Jeff Mesnil Assignee: Jeff Mesnil Fix For: 12.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3324) Add a commands line flag to disable request validation

by ehsavoie Hugonnet (JIRA)

ehsavoie Hugonnet created WFCORE-3324: ----------------------------------------- Summary: Add a commands line flag to disable request validation Key: WFCORE-3324 URL: https://issues.jboss.org/browse/WFCORE-3324 Project: WildFly Core Issue Type: Enhancement Components: CLI Affects Versions: 3.0.3.Final Reporter: ehsavoie Hugonnet Assignee: ehsavoie Hugonnet Priority: Minor While the CLI supports enabling/disabling request validation this behavior can't be set from the command line. A command line flag for this should be added. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3323) Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3323?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-3323: --------------------------------- Description: As part of fix JBEAP-12933 there was added attribute {{mapping-mode="first"}} into "default-permission-mapper" {{simple-permission-mapper}} in default configuration. Value {{first}} is default value of {{simple-permission-mapper.mapping-mode}} which means that this attribute disappears after first change in server configuration. It can be confusing since Elytron subsystem configuration in XML is changed even if there was no request for changing that configuration. Attribute {{mapping-mode="first"}} should be removed from default configuration. (was: As part of fix JBEAP-12933 in EAP 7.1.0.CR2 there was added attribute {{mapping-mode="first"}} into "default-permission-mapper" {{simple-permission-mapper}} in default configuration. Value {{first}} is default value of {{simple-permission-mapper.mapping-mode}} which means that this attribute disappears after first change in server configuration. It can be confusing since Elytron subsystem configuration in XML is changed even if there was no request for changing that configuration. Attribute {{mapping-mode="first"}} should be removed from default configuration.) > Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper > --------------------------------------------------------------------------------------- > > Key: WFCORE-3323 > URL: https://issues.jboss.org/browse/WFCORE-3323 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.3.Final > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Minor > > As part of fix JBEAP-12933 there was added attribute {{mapping-mode="first"}} into "default-permission-mapper" {{simple-permission-mapper}} in default configuration. Value {{first}} is default value of {{simple-permission-mapper.mapping-mode}} which means that this attribute disappears after first change in server configuration. It can be confusing since Elytron subsystem configuration in XML is changed even if there was no request for changing that configuration. Attribute {{mapping-mode="first"}} should be removed from default configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3323) Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper

by Ondrej Lukas (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3323?page=com.atlassian.jira.plugi... ] Ondrej Lukas updated WFCORE-3323: --------------------------------- Affects Version/s: 3.0.3.Final > Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper > --------------------------------------------------------------------------------------- > > Key: WFCORE-3323 > URL: https://issues.jboss.org/browse/WFCORE-3323 > Project: WildFly Core > Issue Type: Bug > Components: Security > Affects Versions: 3.0.3.Final > Reporter: Ondrej Lukas > Assignee: Darran Lofthouse > Priority: Minor > > As part of fix JBEAP-12933 in EAP 7.1.0.CR2 there was added attribute {{mapping-mode="first"}} into "default-permission-mapper" {{simple-permission-mapper}} in default configuration. Value {{first}} is default value of {{simple-permission-mapper.mapping-mode}} which means that this attribute disappears after first change in server configuration. It can be confusing since Elytron subsystem configuration in XML is changed even if there was no request for changing that configuration. Attribute {{mapping-mode="first"}} should be removed from default configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3323) Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper

by Ondrej Lukas (JIRA)

Ondrej Lukas created WFCORE-3323: ------------------------------------ Summary: Initial Elytron configuration includes mapping-mode="first" in simple-permission-mapper Key: WFCORE-3323 URL: https://issues.jboss.org/browse/WFCORE-3323 Project: WildFly Core Issue Type: Bug Components: Security Reporter: Ondrej Lukas Assignee: Darran Lofthouse Priority: Minor As part of fix JBEAP-12933 in EAP 7.1.0.CR2 there was added attribute {{mapping-mode="first"}} into "default-permission-mapper" {{simple-permission-mapper}} in default configuration. Value {{first}} is default value of {{simple-permission-mapper.mapping-mode}} which means that this attribute disappears after first change in server configuration. It can be confusing since Elytron subsystem configuration in XML is changed even if there was no request for changing that configuration. Attribute {{mapping-mode="first"}} should be removed from default configuration. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBJCA-1355) set-tx-query-timeout does not work when the remaining transaction timeout is shorter than one second

by Masafumi Miura (JIRA)

[ https://issues.jboss.org/browse/JBJCA-1355?page=com.atlassian.jira.plugin... ] Masafumi Miura updated JBJCA-1355: ---------------------------------- Git Pull Request: https://github.com/ironjacamar/ironjacamar/pull/637, https://github.com/ironjacamar/ironjacamar/pull/638, https://github.com/ironjacamar/ironjacamar/pull/639 (was: https://github.com/ironjacamar/ironjacamar/pull/637, https://github.com/ironjacamar/ironjacamar/pull/638) > set-tx-query-timeout does not work when the remaining transaction timeout is shorter than one second > ---------------------------------------------------------------------------------------------------- > > Key: JBJCA-1355 > URL: https://issues.jboss.org/browse/JBJCA-1355 > Project: IronJacamar > Issue Type: Bug > Components: JDBC > Reporter: Masafumi Miura > > {{set-tx-query-timeout}} setting does not work when the remaining transaction timeout is shorter than one second (between 0-999 millis) due to incorrect round-up in IronJacamar {{WrapperDataSource#getTimeLeftBeforeTransactionTimeout()}}. > --- > {{WrappedConnection#checkConfiguredQueryTimeout()}} checks the returned value from {{WrapperDataSource#getTimeLeftBeforeTransactionTimeout()}} and set the value to query timeout if it's larger than 0. If it's not larger than 0, the configured query timeout ({{query-timeout}} in datasource setting) is used. This behavior itself is ok. > However, {{WrapperDataSource#getTimeLeftBeforeTransactionTimeout()}} incorrectly rounds up the returned value from transaction manager's {{TransactionTimeoutConfiguration#getTimeLeftBeforeTransactionTimeout()}}. And it results in returning 0 when the remaining transaction timeout is between 0-999 millis. This causes the issue. > Here's the related code from 1.3.7.Final (It's same in the latest 1.3 branch and 1.4 branch): > - https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.7.Final/a... > {code} > 2022 /** > 2023 * Check configured query timeout > 2024 * @param ws The statement > 2025 * @param explicitTimeout An explicit timeout value set > 2026 * @exception SQLException Thrown if an error occurs > 2027 */ > 2028 void checkConfiguredQueryTimeout(WrappedStatement ws, int explicitTimeout) throws SQLException > 2029 { > 2030 if (mc == null || dataSource == null) > 2031 return; > 2032 > 2033 int timeout = 0; > 2034 > 2035 // Use the transaction timeout > 2036 if (mc.isTransactionQueryTimeout()) > 2037 { > 2038 timeout = dataSource.getTimeLeftBeforeTransactionTimeout(); > 2039 if (timeout > 0 && explicitTimeout > 0 && timeout > explicitTimeout) > 2040 timeout = explicitTimeout; > 2041 } > 2042 > 2043 // Look for a configured value > 2044 if (timeout <= 0 && explicitTimeout <= 0) > 2045 timeout = mc.getQueryTimeout(); > 2046 > 2047 if (timeout > 0) > 2048 ws.setQueryTimeout(timeout); > 2049 } > {code} > - https://github.com/ironjacamar/ironjacamar/blob/ironjacamar-1.3.7.Final/a... > {code} > 190 /** > 191 * Get the time left before a transaction timeout > 192 * @return The amount in seconds; <code>-1</code> if no timeout > 193 * @exception SQLException Thrown if an error occurs > 194 */ > 195 protected int getTimeLeftBeforeTransactionTimeout() throws SQLException > 196 { > 197 try > 198 { > 199 if (cm instanceof TransactionTimeoutConfiguration) > 200 { > 201 long timeout = ((TransactionTimeoutConfiguration) cm).getTimeLeftBeforeTransactionTimeout(true); > 202 // No timeout > 203 if (timeout == -1) > 204 return -1; > 205 // Round up to the nearest second > 206 long result = timeout / 1000; > 207 if ((result % 1000) != 0) > 208 ++result; > 209 return (int) result; > 210 } > 211 else > 212 return -1; > 213 } > 214 catch (RollbackException e) > 215 { > 216 throw new SQLException(e); > 217 } > 218 } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

6 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 October 2017