September 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFCORE-3258) ServiceRemoveStepHandler fails to remove services if any associated capabilities use a dynamic name mapper

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3258?page=com.atlassian.jira.plugi... ] Paul Ferraro updated WFCORE-3258: --------------------------------- Git Pull Request: https://github.com/wildfly/wildfly-core/pull/2775 (was: https://github.com/wildfly/wildfly-core/pull/2775, https://github.com/wildfly/wildfly-core/pull/2776) > ServiceRemoveStepHandler fails to remove services if any associated capabilities use a dynamic name mapper > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3258 > URL: https://issues.jboss.org/browse/WFCORE-3258 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3258) ServiceRemoveStepHandler fails to remove services if any associated capabilities use a dynamic name mapper

by Paul Ferraro (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3258?page=com.atlassian.jira.plugi... ] Paul Ferraro reassigned WFCORE-3258: ------------------------------------ Assignee: Paul Ferraro (was: Brian Stansberry) > ServiceRemoveStepHandler fails to remove services if any associated capabilities use a dynamic name mapper > ---------------------------------------------------------------------------------------------------------- > > Key: WFCORE-3258 > URL: https://issues.jboss.org/browse/WFCORE-3258 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 3.0.1.Final > Reporter: Paul Ferraro > Assignee: Paul Ferraro > Priority: Critical > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3258) ServiceRemoveStepHandler fails to remove services if any associated capabilities use a dynamic name mapper

by Paul Ferraro (JIRA)

Paul Ferraro created WFCORE-3258: ------------------------------------ Summary: ServiceRemoveStepHandler fails to remove services if any associated capabilities use a dynamic name mapper Key: WFCORE-3258 URL: https://issues.jboss.org/browse/WFCORE-3258 Project: WildFly Core Issue Type: Bug Components: Domain Management Affects Versions: 3.0.1.Final Reporter: Paul Ferraro Assignee: Brian Stansberry Priority: Critical -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (ELY-1354) Increment WildFly Elytron schema version for client configuration updates

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/ELY-1354?page=com.atlassian.jira.plugin.s... ] Darran Lofthouse updated ELY-1354: ---------------------------------- Summary: Increment WildFly Elytron schema version for client configuration updates (was: Increment WildFly Elytron schema version) > Increment WildFly Elytron schema version for client configuration updates > ------------------------------------------------------------------------- > > Key: ELY-1354 > URL: https://issues.jboss.org/browse/ELY-1354 > Project: WildFly Elytron > Issue Type: Task > Components: Authentication Client > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Fix For: 1.2.0.Beta3 > > > At the same time we need to review how we handle supporting multiple versions. > On one hand we can look at making our parser fairly permissive so if we are just adding it can support both old and new, the biggest advantage here is we can minimise code duplication. > The down side however is in the future it becomes very difficult to reverse and remove support for older schema. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9312) Creating infinispan security cache w/o default cache doesn't use auth-cache settings

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFLY-9312: ---------------------------------------------- Summary: Creating infinispan security cache w/o default cache doesn't use auth-cache settings Key: WFLY-9312 URL: https://issues.jboss.org/browse/WFLY-9312 Project: WildFly Issue Type: Bug Components: Clustering, Security Affects Versions: 11.0.0.CR1 Reporter: Bartosz Spyrko-Śmietanko Assignee: Bartosz Spyrko-Śmietanko If a default cache is not defined on security cache container, cache configuration named 'auth-cache' should be used (based on [1]). However the created cache has default values instead of ones specified on the auth-cache. [1] https://issues.jboss.org/browse/WFLY-9206 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFLY-9311) Creating infinispan security cache w/o default cache doesn't use auth-cache settings

by Bartosz Spyrko-Śmietanko (JIRA)

Bartosz Spyrko-Śmietanko created WFLY-9311: ---------------------------------------------- Summary: Creating infinispan security cache w/o default cache doesn't use auth-cache settings Key: WFLY-9311 URL: https://issues.jboss.org/browse/WFLY-9311 Project: WildFly Issue Type: Bug Components: Clustering, Security Affects Versions: 11.0.0.CR1 Reporter: Bartosz Spyrko-Śmietanko Assignee: Bartosz Spyrko-Śmietanko If a default cache is not defined on security cache container, cache configuration named 'auth-cache' should be used (based on [1]). However the created cache has default values instead of ones specified on the auth-cache. [1] https://issues.jboss.org/browse/WFLY-9206 -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1724) DRL compilation error on a generic type property

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1724?page=com.atlassian.jira.plugi... ] Mario Fusco updated DROOLS-1724: -------------------------------- Sprint: 2017 Week 36-37 > DRL compilation error on a generic type property > ------------------------------------------------ > > Key: DROOLS-1724 > URL: https://issues.jboss.org/browse/DROOLS-1724 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final > Environment: drools 6.5.0.Final / java 1.8.0_131 > Reporter: Ryo Murai > Assignee: Mario Fusco > Fix For: 7.3.1.Final > > > I got a DRL compilation error on accessing through a generic type property. Minimized object definition is below. > {code:borderStyle=solid} > public interface OrderLine<T extends Product> { > T getProduct(); > } > public interface Product { > String getId(); > String getCategory(); > } > // and I have concrete classes, ex. Book, BookOrderLine<Book>, DVD, DVDOrderLine<DVD>, ... etc > {code} > DRL(snippet) is here > {code:borderStyle=solid} > when > $orderLine: OrderLine() > // compilation failed > Product( > id == $orderLine.product.id || category == $orderLine.product.category > ) from discountProducts > {code} > This causes below exception. > {panel} > java.lang.RuntimeException: [Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules/checkorder-not-compiled.drl, line=15, column=0 text=Unable to Analyse Expression id == $orderLine.product.id || category == $orderLine.product.category: > [Error: unable to resolve method using strict-mode: java.lang.Object.category()] > [Near : {... Line.product.id || category == $orderLine.product.category ....}] > ^ > [Line: 15, Column: 2]]] > {panel} > This is weird because it won't occur when the restriction has single condition like below. Drools could analyze this expression. > {code:borderStyle=solid} > when > $orderLine: OrderLine() > // this is compiled, even if `Product(id == $orderLine.product.id)` > Product( > category == $orderLine.product.category > ) from discountProducts > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-1724) DRL compilation error on a generic type property

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1724?page=com.atlassian.jira.plugi... ] Mario Fusco resolved DROOLS-1724. --------------------------------- Fix Version/s: 7.3.1.Final Resolution: Done Fixed in mvel by https://github.com/mvel/mvel/commit/1bcbe976b8e0fcac5cda277b0f604d769a3d2671 > DRL compilation error on a generic type property > ------------------------------------------------ > > Key: DROOLS-1724 > URL: https://issues.jboss.org/browse/DROOLS-1724 > Project: Drools > Issue Type: Bug > Affects Versions: 6.5.0.Final > Environment: drools 6.5.0.Final / java 1.8.0_131 > Reporter: Ryo Murai > Assignee: Mario Fusco > Fix For: 7.3.1.Final > > > I got a DRL compilation error on accessing through a generic type property. Minimized object definition is below. > {code:borderStyle=solid} > public interface OrderLine<T extends Product> { > T getProduct(); > } > public interface Product { > String getId(); > String getCategory(); > } > // and I have concrete classes, ex. Book, BookOrderLine<Book>, DVD, DVDOrderLine<DVD>, ... etc > {code} > DRL(snippet) is here > {code:borderStyle=solid} > when > $orderLine: OrderLine() > // compilation failed > Product( > id == $orderLine.product.id || category == $orderLine.product.category > ) from discountProducts > {code} > This causes below exception. > {panel} > java.lang.RuntimeException: [Message [id=1, kieBase=defaultKieBase, level=ERROR, path=rules/checkorder-not-compiled.drl, line=15, column=0 text=Unable to Analyse Expression id == $orderLine.product.id || category == $orderLine.product.category: > [Error: unable to resolve method using strict-mode: java.lang.Object.category()] > [Near : {... Line.product.id || category == $orderLine.product.category ....}] > ^ > [Line: 15, Column: 2]]] > {panel} > This is weird because it won't occur when the restriction has single condition like below. Drools could analyze this expression. > {code:borderStyle=solid} > when > $orderLine: OrderLine() > // this is compiled, even if `Product(id == $orderLine.product.id)` > Product( > category == $orderLine.product.category > ) from discountProducts > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-3256) Filters.filterToFilterSpec fails if ANY or ALL include legal undefined fields

by James Perkins (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3256?page=com.atlassian.jira.plugi... ] James Perkins commented on WFCORE-3256: --------------------------------------- That is correct that the {{filter}} is the older attribute and {{filter-spec}} should be used. I'll have a look at this though. > Filters.filterToFilterSpec fails if ANY or ALL include legal undefined fields > ----------------------------------------------------------------------------- > > Key: WFCORE-3256 > URL: https://issues.jboss.org/browse/WFCORE-3256 > Project: WildFly Core > Issue Type: Bug > Components: Logging > Reporter: Brian Stansberry > Assignee: James Perkins > Priority: Minor > > Say you have a filter value like this: > {code} > { > "any" => { > "match" => ".*", > "change-level" => undefined, > "level" => undefined, > "level-range" => undefined, > "not" => undefined > }, > "all" => undefined, > "change-level" => undefined, > "level" => undefined, > "level-range" => undefined, > "not" => undefined > } > {code} > Writing that will fail with "WFLYLOG0025: Filter ("change-level" => undefined) is invalid". > This is because filterToFilterSpec will process the "any" node by iterating over its fields and recursing, and as soon as it gets to one of the 'undefined' ones it will fail. But the overall structure should be fine. > I hit this when testing a WFCORE-3255 fix, one that had the effect of adding "change-level" => undefined, etc to the params used by LoggingOperationsSubsystemTestCase.testLegacyFilters. > I can probably work around this easily enough and IIRC this 'filter' stuff is real old, so this is no big deal. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-1399) Failure when resolving an expression with the default value containing a '$' at the end

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFCORE-1399?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on WFCORE-1399: ------------------------------------------------- Petr Penicka <ppenicka(a)redhat.com> changed the Status of [bug 1443209|https://bugzilla.redhat.com/show_bug.cgi?id=1443209] from VERIFIED to CLOSED > Failure when resolving an expression with the default value containing a '$' at the end > --------------------------------------------------------------------------------------- > > Key: WFCORE-1399 > URL: https://issues.jboss.org/browse/WFCORE-1399 > Project: WildFly Core > Issue Type: Bug > Components: Domain Management > Affects Versions: 2.1.0.CR1 > Reporter: Valentin Maechler > Assignee: ehsavoie Hugonnet > Fix For: 2.2.0.CR1, 3.0.0.Alpha1 > > Attachments: ExpressionResolver.java, ExpressionResolverUnitTestCase.java > > > Can not add a JNDI / naming entry which contains a "$" sign at the end of its default value. > e.g. {code} > value="${my.sample.property1:entry5-default-value-with-special-char-at-the-end-$}" > {code} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 10 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 September 2017