November 2016 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-1916) Upgrade to WildFly Elytron 1.1.0.Beta13

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1916?page=com.atlassian.jira.plugi... ] Darran Lofthouse updated WFCORE-1916: ------------------------------------- Summary: Upgrade to WildFly Elytron 1.1.0.Beta13 (was: Upgrade to WildFly Elytron 1.1.0.Beta12) > Upgrade to WildFly Elytron 1.1.0.Beta13 > --------------------------------------- > > Key: WFCORE-1916 > URL: https://issues.jboss.org/browse/WFCORE-1916 > Project: WildFly Core > Issue Type: Component Upgrade > Components: Security > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 3.0.0.Alpha12 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7514) Implement graceful shutdown support for XTS endpoints

by Gytis Trikleris (JIRA)

Gytis Trikleris created WFLY-7514: ------------------------------------- Summary: Implement graceful shutdown support for XTS endpoints Key: WFLY-7514 URL: https://issues.jboss.org/browse/WFLY-7514 Project: WildFly Issue Type: Feature Request Components: XTS Reporter: Gytis Trikleris Assignee: Gytis Trikleris Priority: Critical Fix For: 11.0.0.Alpha1 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7513) Unclear description of cache and cache-container attributes of singleton policy in singleton subsystem

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7513?page=com.atlassian.jira.plugin.... ] Paul Ferraro updated WFLY-7513: ------------------------------- Summary: Unclear description of cache and cache-container attributes of singleton policy in singleton subsystem (was: Not clear description of cache and cache-container attributes of singleton policy in singleton subsystem) > Unclear description of cache and cache-container attributes of singleton policy in singleton subsystem > ------------------------------------------------------------------------------------------------------ > > Key: WFLY-7513 > URL: https://issues.jboss.org/browse/WFLY-7513 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Descriptions of {{cache}} and {{cache-container}} attributes in singleton subsystem should involve dependency between these two attributes. The important information is that if {{cache}} attribute is not defined, {{default-cache}} of {{cache-container}} will be used. Analogically for {{cache}} attribute – it sets cache which have to be available in set {{cache-container}}. > Current state: > {code} > "cache" => { > "type" => STRING, > "description" => "The cache backing the singleton policy's singleton service", > "expressions-allowed" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.clustering.cache.singleton-service-builder-factory", > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "cache-container" => { > "type" => STRING, > "description" => "The cache container backing the singleton policy's singleton service", > "expressions-allowed" => false, > "nillable" => false, > "capability-reference" => "org.wildfly.clustering.cache.default-singleton-service-builder-factory", > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7513) Not clear description of cache and cache-container attributes of singleton policy in singleton subsystem

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFLY-7513?page=com.atlassian.jira.plugin.... ] Paul Ferraro moved JBEAP-6974 to WFLY-7513: ------------------------------------------- Project: WildFly (was: JBoss Enterprise Application Platform) Key: WFLY-7513 (was: JBEAP-6974) Workflow: GIT Pull Request workflow (was: CDW with loose statuses v1) Component/s: Clustering (was: Clustering) (was: User Experience) Affects Version/s: 10.1.0.Final (was: 7.1.0.DR7) > Not clear description of cache and cache-container attributes of singleton policy in singleton subsystem > -------------------------------------------------------------------------------------------------------- > > Key: WFLY-7513 > URL: https://issues.jboss.org/browse/WFLY-7513 > Project: WildFly > Issue Type: Bug > Components: Clustering > Affects Versions: 10.1.0.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > > Descriptions of {{cache}} and {{cache-container}} attributes in singleton subsystem should involve dependency between these two attributes. The important information is that if {{cache}} attribute is not defined, {{default-cache}} of {{cache-container}} will be used. Analogically for {{cache}} attribute – it sets cache which have to be available in set {{cache-container}}. > Current state: > {code} > "cache" => { > "type" => STRING, > "description" => "The cache backing the singleton policy's singleton service", > "expressions-allowed" => false, > "nillable" => true, > "capability-reference" => "org.wildfly.clustering.cache.singleton-service-builder-factory", > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > }, > "cache-container" => { > "type" => STRING, > "description" => "The cache container backing the singleton policy's singleton service", > "expressions-allowed" => false, > "nillable" => false, > "capability-reference" => "org.wildfly.clustering.cache.default-singleton-service-builder-factory", > "min-length" => 1L, > "max-length" => 2147483647L, > "access-type" => "read-write", > "storage" => "configuration", > "restart-required" => "resource-services" > } > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-296) Drools date coercion and conditional OR

by Szymona Wal (JIRA)

[ https://issues.jboss.org/browse/DROOLS-296?page=com.atlassian.jira.plugin... ] Szymona Wal commented on DROOLS-296: ------------------------------------ Hello, is this bug same problem for this issue: http://stackoverflow.com/questions/40483684/drools-or-vs-and-inside-map-c... ? Unfortunatly, I cannot change drools to 6.X, to much effort with API change and logic behind building Knowledgebase, adding, removing, updating. Is it lost in 5.6.X then? > Drools date coercion and conditional OR > --------------------------------------- > > Key: DROOLS-296 > URL: https://issues.jboss.org/browse/DROOLS-296 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final > Environment: Windows 7 > Reporter: Madhura Jayaratne > Assignee: Mario Fusco > Fix For: 6.0.1.Final > > > If I try a simple Drools rule with conditions on date type and uses conditional OR (||) I get the following error. If I change || to && it works fine. > Condition > $container: DateContainer( date >= "15-Oct-2013" || date <= "01-Oct-2013" ) > Error > Unable to Analyse Expression date >= "15-Oct-2013" || date <= "01-Oct-2013": > [Error: Comparison operation requires compatible types. Found class java.util.Date and class java.lang.String] > [Near : {... date >= "15-Oct-2013" || date <= "01-Oct-2013" ....}] > ^ > [Line: 9, Column: 1] : [Rule name='Test rule'] -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFLY-7506) Get rid of temporary ModelUtils and FailedOperationTransformationConfig in EJB 3 transformer tests

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFLY-7506?page=com.atlassian.jira.plugin.... ] Kabir Khan updated WFLY-7506: ----------------------------- Description: WFCORE-1892 introduces new stricter checking which needs some improvements in the EJB3 transformer tests. More functionality has been added to the test framework to make this possible, as an interim solution EJB3 contains a copy of the classes mentioned in this issue, in order to get the tests to pass with the improvements in the EJB3 tests. (was: See https://issues.jboss.org/browse/WFCORE-1950 for explanation. As an interim solution EJB3 contains a copy of these classes) > Get rid of temporary ModelUtils and FailedOperationTransformationConfig in EJB 3 transformer tests > -------------------------------------------------------------------------------------------------- > > Key: WFLY-7506 > URL: https://issues.jboss.org/browse/WFLY-7506 > Project: WildFly > Issue Type: Bug > Reporter: Kabir Khan > Assignee: Kabir Khan > > WFCORE-1892 introduces new stricter checking which needs some improvements in the EJB3 transformer tests. More functionality has been added to the test framework to make this possible, as an interim solution EJB3 contains a copy of the classes mentioned in this issue, in order to get the tests to pass with the improvements in the EJB3 tests. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1950) Get rid of system property for turning off 'strict' transformers rejection testing

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1950?page=com.atlassian.jira.plugi... ] Kabir Khan commented on WFCORE-1950: ------------------------------------ This is no longer relevant > Get rid of system property for turning off 'strict' transformers rejection testing > ---------------------------------------------------------------------------------- > > Key: WFCORE-1950 > URL: https://issues.jboss.org/browse/WFCORE-1950 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha12 > > > WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release with WFCORE-1892. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1950) Get rid of system property for turning off 'strict' transformers rejection testing

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1950?page=com.atlassian.jira.plugi... ] Kabir Khan reopened WFCORE-1950: -------------------------------- > Get rid of system property for turning off 'strict' transformers rejection testing > ---------------------------------------------------------------------------------- > > Key: WFCORE-1950 > URL: https://issues.jboss.org/browse/WFCORE-1950 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha12 > > > WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release with WFCORE-1892. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1950) Get rid of system property for turning off 'strict' transformers rejection testing

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1950?page=com.atlassian.jira.plugi... ] Kabir Khan closed WFCORE-1950. ------------------------------ Resolution: Won't Do > Get rid of system property for turning off 'strict' transformers rejection testing > ---------------------------------------------------------------------------------- > > Key: WFCORE-1950 > URL: https://issues.jboss.org/browse/WFCORE-1950 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha12 > > > WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release with WFCORE-1892. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1950) Get rid of system property for turning off 'strict' transformers rejection testing

by Kabir Khan (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1950?page=com.atlassian.jira.plugi... ] Kabir Khan closed WFCORE-1950. ------------------------------ Resolution: Done THis is no longer relevant > Get rid of system property for turning off 'strict' transformers rejection testing > ---------------------------------------------------------------------------------- > > Key: WFCORE-1950 > URL: https://issues.jboss.org/browse/WFCORE-1950 > Project: WildFly Core > Issue Type: Task > Components: Domain Management > Reporter: Kabir Khan > Assignee: Kabir Khan > Fix For: 3.0.0.Alpha12 > > > WFCORE-1892 reworks the rejection transformers testing, and tightens it up a bit. Most things work fine with this stricter checking, apart from ejb3 which needs reworking. To get around this WFCORE-1892 has a temporary system property to disable this stricter checking. This work lives in my WFCORE-1892-investigation for merging after we have a core release with WFCORE-1892. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 8 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 November 2016