August 2019 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFBUILD-48) Integrate interfaces and [outbound-]socket-bindings configured in the template with those from subsystems

by Brian Stansberry (Jira)

Brian Stansberry created WFBUILD-48: --------------------------------------- Summary: Integrate interfaces and [outbound-]socket-bindings configured in the template with those from subsystems Key: WFBUILD-48 URL: https://issues.jboss.org/browse/WFBUILD-48 Project: WildFly Build Tools Issue Type: Enhancement Reporter: Brian Stansberry Assignee: Brian Stansberry ConfigurationAssembler sorts the interfaces and [outbound-]socket-bindings coming from subsystems alphabetically, but those configured directly in the template are added first. The result is not all are alphabetized. WFCORE-4624 will result in WildFly persisting alphabetically so we want to original config to be that way as well. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4625) Expose a util method for standard marshalling of xml element content

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4625: ---------------------------------------- Summary: Expose a util method for standard marshalling of xml element content Key: WFCORE-4625 URL: https://issues.jboss.org/browse/WFCORE-4625 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Staxmappers' XMLElementWriter.writeCharacters(String) puts content on a new line. But DefaultAttributeMarshaller ensures this is only called if the content includes a newline; otherwise it uses a different method that keeps the content inline with the containing element. Expose the DefaultAttributeMarshaller behavior so other attribute marshallers can use it. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4624) Perist interfaces and socket-bindings in alphabetical order

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4624?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4624: ------------------------------------- Description: Similar to other config element types where Galleon inputs to the config are coming from disparate sources (e.g. subsystems, socket bindings), persist the interface and [xxx-]socket-binding elements in alphabetical order to avoid meaningless differences between configs. (was: Similar to other config element types where Galleon inputs to the config are coming from disparate sources (e.g. subsystems, socket bindings), persist the elements in alphabetical order to avoid meaningless differences between configs.) > Perist interfaces and socket-bindings in alphabetical order > ----------------------------------------------------------- > > Key: WFCORE-4624 > URL: https://issues.jboss.org/browse/WFCORE-4624 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > Similar to other config element types where Galleon inputs to the config are coming from disparate sources (e.g. subsystems, socket bindings), persist the interface and [xxx-]socket-binding elements in alphabetical order to avoid meaningless differences between configs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4624) Perist interfaces and socket-bindings in alphabetical order

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFCORE-4624?page=com.atlassian.jira.plugi... ] Brian Stansberry updated WFCORE-4624: ------------------------------------- Summary: Perist interfaces and socket-bindings in alphabetical order (was: Perist interfaces in alphabetical order) > Perist interfaces and socket-bindings in alphabetical order > ----------------------------------------------------------- > > Key: WFCORE-4624 > URL: https://issues.jboss.org/browse/WFCORE-4624 > Project: WildFly Core > Issue Type: Enhancement > Components: Management > Reporter: Brian Stansberry > Assignee: Brian Stansberry > Priority: Minor > > Similar to other config element types where Galleon inputs to the config are coming from disparate sources (e.g. subsystems, socket bindings), persist the elements in alphabetical order to avoid meaningless differences between configs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4469) Invalid result with collect, mvel and ForceEagerActivationOption.YES

by Martin Weiler (Jira)

Martin Weiler created DROOLS-4469: ------------------------------------- Summary: Invalid result with collect, mvel and ForceEagerActivationOption.YES Key: DROOLS-4469 URL: https://issues.jboss.org/browse/DROOLS-4469 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.25.0.Final Reporter: Martin Weiler Assignee: Mario Fusco A rule updates a list in a fact: {noformat} rule "Init" dialect "mvel" when $fl: FactWithList(items.size()==0) then $fl.getItems().add("A"); $fl.getItems().add("B"); update($fl); end {noformat} A second rule verifies if other facts exist, matching the items in the updated list: {noformat} rule "Expected Outcome" dialect "mvel" when $fl: FactWithList($itemList : items != null) $l: java.util.ArrayList(size > 0) from collect(FactWithString($itemList contains stringValue)); then System.out.println("--> Rule: " + kcontext.getRule().getName() + " fired, " + $fl + ", collect list: " + $l.size()); end {noformat} This rule is *not* fired if * mvel dialect is used *and* * Drools is executed with {{ForceEagerActivationOption.YES}} (jBPM use case) Note: This worked in 7.17 and earlier! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4468) Invalid result with collect, mvel and ForceEagerActivationOption.YES

by Martin Weiler (Jira)

Martin Weiler created DROOLS-4468: ------------------------------------- Summary: Invalid result with collect, mvel and ForceEagerActivationOption.YES Key: DROOLS-4468 URL: https://issues.jboss.org/browse/DROOLS-4468 Project: Drools Issue Type: Bug Components: core engine Affects Versions: 7.25.0.Final Reporter: Martin Weiler Assignee: Mario Fusco Attachments: case02445433-testcase.zip A rule updates a list in a fact: {noformat} rule "Init" dialect "mvel" when $fl: FactWithList(items.size()==0) then $fl.getItems().add("A"); $fl.getItems().add("B"); update($fl); end {noformat} A second rule verifies if other facts exist, matching the items in the updated list: {noformat} rule "Expected Outcome" dialect "mvel" when $fl: FactWithList($itemList : items != null) $l: java.util.ArrayList(size > 0) from collect(FactWithString($itemList contains stringValue)); then System.out.println("--> Rule: " + kcontext.getRule().getName() + " fired, " + $fl + ", collect list: " + $l.size()); end {noformat} This rule is *not* fired if * mvel dialect is used *and* * Drools is executed with {{ForceEagerActivationOption.YES}} (jBPM use case) Note: This worked in 7.17 and earlier! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-4468) Invalid result with collect, mvel and ForceEagerActivationOption.YES

by Martin Weiler (Jira)

[ https://issues.jboss.org/browse/DROOLS-4468?page=com.atlassian.jira.plugi... ] Martin Weiler updated DROOLS-4468: ---------------------------------- Attachment: case02445433-testcase.zip > Invalid result with collect, mvel and ForceEagerActivationOption.YES > -------------------------------------------------------------------- > > Key: DROOLS-4468 > URL: https://issues.jboss.org/browse/DROOLS-4468 > Project: Drools > Issue Type: Bug > Components: core engine > Affects Versions: 7.25.0.Final > Reporter: Martin Weiler > Assignee: Mario Fusco > Priority: Major > Attachments: case02445433-testcase.zip > > > A rule updates a list in a fact: > {noformat} > rule "Init" > dialect "mvel" > when > $fl: FactWithList(items.size()==0) > then > $fl.getItems().add("A"); > $fl.getItems().add("B"); > update($fl); > end > {noformat} > A second rule verifies if other facts exist, matching the items in the updated list: > {noformat} > rule "Expected Outcome" > dialect "mvel" > when > $fl: FactWithList($itemList : items != null) > $l: java.util.ArrayList(size > 0) from collect(FactWithString($itemList contains stringValue)); > then > System.out.println("--> Rule: " + kcontext.getRule().getName() + " fired, " + $fl + ", collect list: " + $l.size()); > end > {noformat} > This rule is *not* fired if > * mvel dialect is used *and* > * Drools is executed with {{ForceEagerActivationOption.YES}} (jBPM use case) > Note: This worked in 7.17 and earlier! -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFBUILD-37) Detect JDK and always-present modules

by Brian Stansberry (Jira)

[ https://issues.jboss.org/browse/WFBUILD-37?page=com.atlassian.jira.plugin... ] Brian Stansberry reassigned WFBUILD-37: --------------------------------------- Fix Version/s: 1.2.10.Final Assignee: David Lloyd Resolution: Done > Detect JDK and always-present modules > ------------------------------------- > > Key: WFBUILD-37 > URL: https://issues.jboss.org/browse/WFBUILD-37 > Project: WildFly Build Tools > Issue Type: Enhancement > Reporter: David Lloyd > Assignee: David Lloyd > Priority: Major > Fix For: 1.2.10.Final > > > Starting (probably) with jboss-modules 1.8, there will be a number of modules which are implicitly declared (with no corresponding {{module.xml}} file). The build tool will fail at this point with the error that there are modules missing any time one of these modules are used. Add a static list of implicit modules for now. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFCORE-4624) Perist interfaces in alphabetical order

by Brian Stansberry (Jira)

Brian Stansberry created WFCORE-4624: ---------------------------------------- Summary: Perist interfaces in alphabetical order Key: WFCORE-4624 URL: https://issues.jboss.org/browse/WFCORE-4624 Project: WildFly Core Issue Type: Enhancement Components: Management Reporter: Brian Stansberry Assignee: Brian Stansberry Similar to other config element types where Galleon inputs to the config are coming from disparate sources (e.g. subsystems, socket bindings), persist the elements in alphabetical order to avoid meaningless differences between configs. -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 months

1
0
0 / 0

[JBoss JIRA] (WFLY-12063) ClassFormatError on JDK13

by Richard Opalka (Jira)

[ https://issues.jboss.org/browse/WFLY-12063?page=com.atlassian.jira.plugin... ] Richard Opalka commented on WFLY-12063: --------------------------------------- Any chance [~smarlow] this issue will be solved till WildFly final release? > ClassFormatError on JDK13 > ------------------------- > > Key: WFLY-12063 > URL: https://issues.jboss.org/browse/WFLY-12063 > Project: WildFly > Issue Type: Bug > Components: JPA / Hibernate > Reporter: Richard Opalka > Assignee: Scott Marlow > Priority: Critical > Labels: blocker-WF18 > Attachments: server.log, test.log > > > The following commit https://github.com/wildfly/wildfly/commit/b6d141b06404a4c23ead1d04d6e26fc... introduced JDK13 regression in WildFly. > Affected tests are: > --- > [ERROR] Errors: > [ERROR] MultiplePuTestCase.org.jboss.as.test.integration.jpa.basic.multiplepersistenceunittest.MultiplePuTestCase » Deployment > [ERROR] EntityListenersTestCase.org.jboss.as.test.integration.jpa.entitylistener.EntityListenersTestCase » Deployment > [ERROR] EPCPropagationTestCase.org.jboss.as.test.integration.jpa.epcpropagation.EPCPropagationTestCase » Deployment > [ERROR] AuditJoinTableoverBidirectionalTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverBidirectionalTest » Deployment > [ERROR] AuditJoinTableoverOnetoManyJoinColumnTest.org.jboss.as.test.integration.jpa.hibernate.envers.AuditJoinTableoverOnetoManyJoinColumnTest » Deployment > [ERROR] ManagementTestCase.getEntityInsertCountAttribute:98 » Deployment Cannot deploy... > [ERROR] JPA2LCTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JPA2LCTestCase » Deployment > [ERROR] JpaStatisticsTestCase.org.jboss.as.test.integration.jpa.secondlevelcache.JpaStatisticsTestCase » Deployment > [ERROR] TransactionTestCase.org.jboss.as.test.integration.jpa.transaction.TransactionTestCase » Deployment > [INFO] > [ERROR] Tests run: 1553, Failures: 0, Errors: 9, Skipped: 14 > --- -- This message was sent by Atlassian Jira (v7.12.1#712002)

6 years, 11 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 August 2019