October 2017 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-9406) [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1)

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9406?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9406: ----------------------------------- Component/s: JPA / Hibernate This also needs an ok from [~smarlow] as the org.eclipse.persistence module has a dep on asm.asm. {code} $ git grep asm.asm feature-pack/src/main/resources/modules/system/layers/base/asm/asm/main/module.xml:<module xmlns="urn:jboss:module:1.5" name="asm.asm"> feature-pack/src/main/resources/modules/system/layers/base/asm/asm/main/module.xml: <artifact name="${asm:asm}"/> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/impl/main/module.xml: <module name="asm.asm" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/main/module.xml: <module name="asm.asm" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/services-sts/main/module.xml: <module name="asm.asm" /> feature-pack/src/main/resources/modules/system/layers/base/org/apache/cxf/ws-security/main/module.xml: <module name="asm.asm" /> feature-pack/src/main/resources/modules/system/layers/base/org/eclipse/persistence/main/module.xml: <module name="asm.asm"/> feature-pack/src/main/resources/modules/system/layers/base/org/jboss/as/webservices/server/integration/main/module.xml: <module name="asm.asm" export="true"/> testsuite/compat/src/test/scripts/build-jars.xml:<module name="asm.asm"/> {code} > [WildFly 11] Upgrade ASM with Version 5.2 (unable to use Arquillian+JaCoCo with ASM 3.3.1) > ------------------------------------------------------------------------------------------ > > Key: WFLY-9406 > URL: https://issues.jboss.org/browse/WFLY-9406 > Project: WildFly > Issue Type: Component Upgrade > Components: Build System, JPA / Hibernate, Web Services > Affects Versions: 11.0.0.CR1 > Reporter: Tibor Digana > Assignee: Alessio Soldano > Priority: Minor > Fix For: 12.0.0.Alpha1 > > > Reported in GitHub https://github.com/wildfly/wildfly/issues/10531 > Arquillian dependends on JaCoCo does not work on WildFLy because AS uses ASM 3.3.1 and JaCoCo uses ASM 5.2. > The class {{org.jacoco.core.internal.flow.ClassProbesVisitor}} extends ASM class {{org.objectweb.asm.ClassVisitor}}. The problem is that {{ClassVisitor}} is interface in ASM 3.3.1. > Please upgrade it in POM: > https://github.com/wildfly/wildfly/blob/master/pom.xml -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-8954) Wildfly 10 with eclipselink Onscucess observer gets stale entity

by Nuno Godinho de Matos (JIRA)

[ https://issues.jboss.org/browse/WFLY-8954?page=com.atlassian.jira.plugin.... ] Nuno Godinho de Matos commented on WFLY-8954: --------------------------------------------- Hi Are there any plans on assimilating the pull request for this issue? NOTE: I will now open another issue - related to extreme cost of creating the first entity manager - for which the core of the issue seems to be on eclipselink org.eclipse.persistence.platform.server.JMXServerPlatformBase but that can be addressed by tweaking org.jipijapa.eclipselink.WildFlyServerPlatform. > Wildfly 10 with eclipselink Onscucess observer gets stale entity > ---------------------------------------------------------------- > > Key: WFLY-8954 > URL: https://issues.jboss.org/browse/WFLY-8954 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Affects Versions: 10.0.0.Final > Reporter: Nuno Godinho de Matos > Assignee: Scott Marlow > > Hi, > In widlfly there seems to be an important issue concerning CDI events and observing these events during onsuccess. At least while using eclipselink. > When using wildfly 10.0.0.Final together with eclipselink, if an application modifies an entity A, fires an event stating entity A has been modified, and an observer consumes this event during transaction success. > Then the observer will be working with stale entities that do not reflect the modifications done to the entity. > A sample application for this issue is available in: > https://github.com/99sono/wildfly10-observe-on-success-stale-entity > The widlfly configuration xml for the sample application, is available in the application itself, as can be seen in the readme documentation. > Many thanks for taking a look. > Kindest regards. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

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

by Stylianos Koussouris (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1663?page=com.atlassian.jira.plugi... ] Stylianos Koussouris commented on DROOLS-1663: ---------------------------------------------- Hey Alexandros, How is that going to affect the guys in The Hague? Have we got a way to mitigate this? How far from releasing are they? I am assuming you guys are aware of the lack of this functionality and have found a workaround? Regards, Stelios On Mon, Oct 2, 2017 at 1:43 PM, Edson Tirelli (JIRA) <issues(a)jboss.org> > 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)

8 years

1
0
0 / 0

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

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-3323?page=com.atlassian.jira.plugi... ] Brian Stansberry commented on WFCORE-3323: ------------------------------------------ Just a note on requirements: if an item in the parsed configuration is not persisted when the xml is rewritten, that's a bug in the code not in the original configuration. IOW the fix isn't to change our standard configuration. BTW, let's call the .xml files we ship our "standard configuration" not our "default configuration". The term "default configuration" is technically correct but using a different term helps avoid confusion about the word default. Attributes in our management model can have default values, and that is a different thing from the standard xml files we ship. > 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)

8 years

1
0
0 / 0

[JBoss JIRA] (WFLY-9405) NPE when trying to recursively remove the EJB subsystem

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFLY-9405?page=com.atlassian.jira.plugin.... ] Brian Stansberry updated WFLY-9405: ----------------------------------- Workaround Description: Put the server in admin-only mode before removing the subsystem. {code} [standalone@localhost:9990 /] reload --admin-only=true [standalone@localhost:9990 /] /subsystem=ejb3:remove {"outcome" => "success"} {code} Putting the server in admin-only before doing this kind of surgery is a good idea anyway. was: Put the server in admin-only mode before removing the subsystem. {code} [standalone@localhost:9990 /] reload --admin-only=true [standalone@localhost:9990 /] /subsystem=ejb3:remove {"outcome" => "success"} {code} Putting the server in admin-only before doing this kind of surgery is probably a good idea anyway. > NPE when trying to recursively remove the EJB subsystem > ------------------------------------------------------- > > Key: WFLY-9405 > URL: https://issues.jboss.org/browse/WFLY-9405 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 11.0.0.CR1 > Reporter: Brian Stansberry > Assignee: Brian Stansberry > > This fails: > {code} > [standalone@localhost:9990 /] /subsystem=ejb3:remove > { > "outcome" => "failed", > "failure-description" => "WFLYCTL0158: Operation handler failed: java.lang.NullPointerException", > "rolled-back" => true > } > {code} > with this in the server log: > {code} > 15:53:42,572 ERROR [org.jboss.as.controller.management-operation] (management-handler-thread - 4) WFLYCTL0013: Operation ("remove") failed - address: ([ > ("subsystem" => "ejb3"), > ("service" => "remote"), > ("channel-creation-options" => "MAX_OUTBOUND_MESSAGES") > ]): java.lang.NullPointerException > at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:894) > at org.jboss.as.controller.OperationContextImpl.readResourceFromRoot(OperationContextImpl.java:884) > at org.jboss.as.controller.RestartParentResourceHandlerBase.getModel(RestartParentResourceHandlerBase.java:216) > at org.jboss.as.controller.RestartParentResourceHandlerBase.access$000(RestartParentResourceHandlerBase.java:39) > at org.jboss.as.controller.RestartParentResourceHandlerBase$1.execute(RestartParentResourceHandlerBase.java:66) > at org.jboss.as.controller.AbstractOperationContext.executeStep(AbstractOperationContext.java:980) > at org.jboss.as.controller.AbstractOperationContext.processStages(AbstractOperationContext.java:726) > at org.jboss.as.controller.AbstractOperationContext.executeOperation(AbstractOperationContext.java:450) > at org.jboss.as.controller.OperationContextImpl.executeOperation(OperationContextImpl.java:1402) > at org.jboss.as.controller.ModelControllerImpl.internalExecute(ModelControllerImpl.java:418) > ... > {code} > I believe a post-boot add of this resource would fail as well. > Problem is ChannelCreationOptionRemove and ChannelCreationOptionAdd in RemoteConnectorChannelCreationOptionResource use an incorrect parentKeyName. These handlers extend RestartParentResourceHandlerBase but are passing the *value* of the parent element as "parentKeyName" instead of its *key*; i.e. "remote" instead of "service". > Even though this code has been like this since 2012, this is somewhat a regression since before the current version our standard configs did not include resources of this type. So users could hit this in previous releases but now they are more likely to. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1730) Cyclic information requirement generates a stackoverflow

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1730?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1730: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41 (was: 2017 Week 36-37, 2017 Week 38-39) > Cyclic information requirement generates a stackoverflow > -------------------------------------------------------- > > Key: DROOLS-1730 > URL: https://issues.jboss.org/browse/DROOLS-1730 > Project: Drools > Issue Type: Bug > Components: dmn engine > Reporter: Mélanie Gauthier > Assignee: Edson Tirelli > > If you have Decision A -> Decision B -> Decision A this causes a stackoverflow when executing it at org.kie.dmn.core.impl.DMNRuntimeImpl.evaluateDecision(DMNRuntimeImpl.java:282) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1701) Code generation and compilation

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1701?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1701: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41 (was: 2017 Week 36-37, 2017 Week 38-39) > Code generation and compilation > ------------------------------- > > Key: DROOLS-1701 > URL: https://issues.jboss.org/browse/DROOLS-1701 > Project: Drools > Issue Type: Task > Components: dmn engine > Reporter: Matteo Mortari > Assignee: Matteo Mortari > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1679) FEEL list filter returns empty collection when there are errors evaluating filter

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1679?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1679: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41 (was: 2017 Week 36-37, 2017 Week 38-39) > FEEL list filter returns empty collection when there are errors evaluating filter > --------------------------------------------------------------------------------- > > Key: DROOLS-1679 > URL: https://issues.jboss.org/browse/DROOLS-1679 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Priority: Minor > Fix For: 7.4.0.Final > > > When having this FEEL list with filter which is incorrect: > {code:java} > ["a", "b", "c"][a] > {code} > the evaluation returns an empty list instead of null. Output of this test is here: > https://gist.github.com/baldimir/18232741fdf1b425ba84d00d83edb939 > I will provide PR with a reproducer today. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1678) Unary test "in" defined before variable throws NPE

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1678?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1678: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41 (was: 2017 Week 36-37, 2017 Week 38-39) > Unary test "in" defined before variable throws NPE > -------------------------------------------------- > > Key: DROOLS-1678 > URL: https://issues.jboss.org/browse/DROOLS-1678 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Fix For: 7.4.0.Final > > > Having this DMN test with Unary test defined: > {code:java} > { test : in x, y : 20, x : [10, 20, 30], result : test( y ) }.result > {code} > The test fails on NPE with the following stacktrace: > https://gist.github.com/baldimir/630c68e766285e430a1755924ea9a66b -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

[JBoss JIRA] (DROOLS-1670) FEEL expression 1 ++++++ 2 passes with result 3

by Kris Verlaenen (JIRA)

[ https://issues.jboss.org/browse/DROOLS-1670?page=com.atlassian.jira.plugi... ] Kris Verlaenen updated DROOLS-1670: ----------------------------------- Sprint: 2017 Week 36-37, 2017 Week 38-39, 2017 Week 40-41 (was: 2017 Week 36-37, 2017 Week 38-39) > FEEL expression 1 ++++++ 2 passes with result 3 > ----------------------------------------------- > > Key: DROOLS-1670 > URL: https://issues.jboss.org/browse/DROOLS-1670 > Project: Drools > Issue Type: Bug > Components: dmn engine > Affects Versions: 7.1.0.Final > Reporter: Tibor Zimányi > Assignee: Edson Tirelli > Priority: Minor > Labels: reported-by-qe > > When evaluating FEEL expression "1 ++++++ 2", the result is 3. This is grammatically correct, but it doesn't look good. I will provide PR with a reproducer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-jira October 2017