September 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-598) accumuate function not working when object chaining is used as accumulate condition

by John Le (JIRA)

[ https://issues.jboss.org/browse/DROOLS-598?page=com.atlassian.jira.plugin... ] John Le commented on DROOLS-598: -------------------------------- Davide - this is where I obtained the jar from http://downloads.jboss.org/drools/release/snapshot/master/jbpm-6.2.0-SNAP.... Please accept my appololy, if this is not where i should download the night build snapshot from. > accumuate function not working when object chaining is used as accumulate condition > ----------------------------------------------------------------------------------- > > Key: DROOLS-598 > URL: https://issues.jboss.org/browse/DROOLS-598 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta2, 6.2.0.CR1, 6.2.0.Final > Reporter: John Le > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.2.0.CR1 > > Attachments: AccumulateWithPassAndFail.java, ShouldFireButNot.java, SumOfAllIssue.java > > > Please see attached code file to reproduce issue. Rule is supposed to fire and yield 0.0 as the sum but rule does not. If we remove TestA, TestB, TestC and leave only TestD as condition then rule fire. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-598) accumuate function not working when object chaining is used as accumulate condition

by John Le (JIRA)

[ https://issues.jboss.org/browse/DROOLS-598?page=com.atlassian.jira.plugin... ] John Le commented on DROOLS-598: -------------------------------- I downloaded the latest nightly build snaphot and it is still not working. To avoid confusion, i uploaded another reproducer ShouldFireButNot.java. As the name implies, when you run the reproducer the rule should fire but it does not because of the impeding defect. Below is what i observed from the log with no traces of rule fire. 2014-09-22 12:13:06 INFO KieRepositoryImpl:73 - KieModule was added:MemoryKieModule[ ReleaseId=org.default:artifact:1.0.0-SNAPSHOT] 2014-09-22 12:13:07 INFO WorkingMemoryConsoleLogger:51 - OBJECT ASSERTED value:TestA factId: 1 2014-09-22 12:13:07 INFO WorkingMemoryConsoleLogger:51 - OBJECT ASSERTED value:TestB factId: 2 2014-09-22 12:13:07 INFO WorkingMemoryConsoleLogger:51 - OBJECT ASSERTED value:TestC factId: 3 2014-09-22 12:13:07 INFO WorkingMemoryConsoleLogger:51 - OBJECT ASSERTED value:TestD factId: 4 > accumuate function not working when object chaining is used as accumulate condition > ----------------------------------------------------------------------------------- > > Key: DROOLS-598 > URL: https://issues.jboss.org/browse/DROOLS-598 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta2, 6.2.0.CR1, 6.2.0.Final > Reporter: John Le > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.2.0.CR1 > > Attachments: AccumulateWithPassAndFail.java, ShouldFireButNot.java, SumOfAllIssue.java > > > Please see attached code file to reproduce issue. Rule is supposed to fire and yield 0.0 as the sum but rule does not. If we remove TestA, TestB, TestC and leave only TestD as condition then rule fire. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-598) accumuate function not working when object chaining is used as accumulate condition

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-598?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-598: --------------------------------------- John, I just tested your latest "ShouldFireButNot" reproducer with 6.2.0-SNAPSHOT with code rebased this very morning. The rule fires once with result 0.0 Which version are you using? Can you please check that it includes the fix done by Mario? Its backport to older, already released versions usually takes more time since it has to go through an approval process (if ever). Thanks Davide > accumuate function not working when object chaining is used as accumulate condition > ----------------------------------------------------------------------------------- > > Key: DROOLS-598 > URL: https://issues.jboss.org/browse/DROOLS-598 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta2, 6.2.0.CR1, 6.2.0.Final > Reporter: John Le > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.2.0.CR1 > > Attachments: AccumulateWithPassAndFail.java, ShouldFireButNot.java, SumOfAllIssue.java > > > Please see attached code file to reproduce issue. Rule is supposed to fire and yield 0.0 as the sum but rule does not. If we remove TestA, TestB, TestC and leave only TestD as condition then rule fire. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-598) accumuate function not working when object chaining is used as accumulate condition

by John Le (JIRA)

[ https://issues.jboss.org/browse/DROOLS-598?page=com.atlassian.jira.plugin... ] John Le updated DROOLS-598: --------------------------- Attachment: ShouldFireButNot.java > accumuate function not working when object chaining is used as accumulate condition > ----------------------------------------------------------------------------------- > > Key: DROOLS-598 > URL: https://issues.jboss.org/browse/DROOLS-598 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta2, 6.2.0.CR1, 6.2.0.Final > Reporter: John Le > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.2.0.CR1 > > Attachments: AccumulateWithPassAndFail.java, ShouldFireButNot.java, SumOfAllIssue.java > > > Please see attached code file to reproduce issue. Rule is supposed to fire and yield 0.0 as the sum but rule does not. If we remove TestA, TestB, TestC and leave only TestD as condition then rule fire. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-119) Add resolve-expressions param to operation read-resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-119?page=com.atlassian.jira.plugin... ] Brian Stansberry updated WFCORE-119: ------------------------------------ Component/s: CLI > Add resolve-expressions param to operation read-resource > -------------------------------------------------------- > > Key: WFCORE-119 > URL: https://issues.jboss.org/browse/WFCORE-119 > Project: WildFly Core > Issue Type: Feature Request > Components: CLI, Domain Management > Reporter: Michael Voegele > Assignee: Joe Wertz > Labels: expression, read-resource > > When reading a resource remotely, it would be nice to have the possibility to have expressions resolved. > Following does of course not work, as the code runs in a separate jvm. > {code:java} > private void readRecursive(ModelNode modelNode, String modelNodeName, Map<String, Object> map) { > switch (modelNode.getType()) { > ... > case EXPRESSION: > // this would be great but won't work as it runs in a different jvm > // ModelNode expression = modelNode.resolve(); > // readRecursive(expression, modelNodeName, map); > map.put(modelNodeName, modelNode.asString()); > break; > ... > } > {code} > Therefore a param resolve-expressions for the read-resource operation would be good. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFCORE-119) Add resolve-expressions param to operation read-resource

by Brian Stansberry (JIRA)

[ https://issues.jboss.org/browse/WFCORE-119?page=com.atlassian.jira.plugin... ] Brian Stansberry moved WFLY-1069 to WFCORE-119: ----------------------------------------------- Project: WildFly Core (was: WildFly) Key: WFCORE-119 (was: WFLY-1069) Component/s: Domain Management (was: Domain Management) > Add resolve-expressions param to operation read-resource > -------------------------------------------------------- > > Key: WFCORE-119 > URL: https://issues.jboss.org/browse/WFCORE-119 > Project: WildFly Core > Issue Type: Feature Request > Components: Domain Management > Reporter: Michael Voegele > Assignee: Joe Wertz > Labels: expression, read-resource > > When reading a resource remotely, it would be nice to have the possibility to have expressions resolved. > Following does of course not work, as the code runs in a separate jvm. > {code:java} > private void readRecursive(ModelNode modelNode, String modelNodeName, Map<String, Object> map) { > switch (modelNode.getType()) { > ... > case EXPRESSION: > // this would be great but won't work as it runs in a different jvm > // ModelNode expression = modelNode.resolve(); > // readRecursive(expression, modelNodeName, map); > map.put(modelNodeName, modelNode.asString()); > break; > ... > } > {code} > Therefore a param resolve-expressions for the read-resource operation would be good. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (DROOLS-598) accumuate function not working when object chaining is used as accumulate condition

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-598?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-598. -------------------------------- Resolution: Done I retested your original AccumulateWithPassAndFail.java test case on master and I confirm it works as expected. Also note that I enforced a compilaton check, so now it is mandatory to separate the patterns and the accumulation function with a ; inside the accumulate. For insance this means that the following drl is no longer valid {code} TestD( parentId == $testC.myId ,$count : count ,count != -999 ) sum($count)) {code} but it is necessary to add a ';' after the pattern inside the accumulate as it follows. {code} TestD( parentId == $testC.myId ,$count : count ,count != -999 ); sum($count)) {code} > accumuate function not working when object chaining is used as accumulate condition > ----------------------------------------------------------------------------------- > > Key: DROOLS-598 > URL: https://issues.jboss.org/browse/DROOLS-598 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.Beta2, 6.2.0.CR1, 6.2.0.Final > Reporter: John Le > Assignee: Mario Fusco > Labels: backport-to-6.0.x > Fix For: 6.2.0.CR1 > > Attachments: AccumulateWithPassAndFail.java, SumOfAllIssue.java > > > Please see attached code file to reproduce issue. Rule is supposed to fire and yield 0.0 as the sum but rule does not. If we remove TestA, TestB, TestC and leave only TestD as condition then rule fire. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3781) Better warning message in add-user.sh

by Darran Lofthouse (JIRA)

[ https://issues.jboss.org/browse/WFLY-3781?page=com.atlassian.jira.plugin.... ] Darran Lofthouse updated WFLY-3781: ----------------------------------- Assignee: (was: Darran Lofthouse) > Better warning message in add-user.sh > ------------------------------------- > > Key: WFLY-3781 > URL: https://issues.jboss.org/browse/WFLY-3781 > Project: WildFly > Issue Type: Feature Request > Components: Scripts > Affects Versions: 8.1.0.Final > Environment: Linux > Reporter: David Tonhofer > Priority: Minor > Fix For: Awaiting Volunteers > > > If (shell or environment) variable JBOSS_HOME is set to something unexpected, then add-user.sh complains: > "WARNING JBOSS_HOME may be pointing to a different installation - unpredictable results may occur." > This can be made clearer, e.g.: > "WARNING: The JBOSS_HOME (/usr/java/jboss7) that this script will use may indicate a different installation than the one this script resides in (/usr/local/java/wildfly) - unpredictable results may occur." > Change of line 35 in "bin/add-user.sh": > echo "WARNING: The JBOSS_HOME ($SANITIZED_JBOSS_HOME) that this script will use may indicate a different installation than the one this script resides in ($RESOLVED_JBOSS_HOME) - unpredictable results may occur." -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on WFLY-3189: ----------------------------------- https://github.com/wildfly/wildfly/pull/6720 which represents the addition of the urn:clustering xsd, has been rejected. The wildfly team opted instead to update the online example documentation. https://github.com/wildfly/wildfly/pull/6739 has been merged. The metadata PR has not yet been accepted. > Error validating jboss-ejb3.xml. > -------------------------------- > > Key: WFLY-3189 > URL: https://issues.jboss.org/browse/WFLY-3189 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Environment: WildFly 8.0.0.Final > Reporter: shinzey shinzey > Assignee: David Lloyd > Attachments: p.patch > > > I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error: > {noformat} > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33] > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37] > src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39] > {noformat} > The jboss-ejb3.xml is quite simple: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:s="urn:security:1.1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> > <assembly-descriptor> > <s:security> > <ejb-name>*</ejb-name> > <s:security-domain>testsd</s:security-domain> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (WFLY-3189) Error validating jboss-ejb3.xml.

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/WFLY-3189?page=com.atlassian.jira.plugin.... ] Rob Stryker updated WFLY-3189: ------------------------------ Git Pull Request: https://github.com/wildfly/wildfly/pull/6720, https://github.com/wildfly/wildfly/pull/6739, https://github.com/jboss/metadata/pull/72 (was: https://github.com/wildfly/wildfly/pull/6720, https://github.com/jboss/metadata/pull/72) > Error validating jboss-ejb3.xml. > -------------------------------- > > Key: WFLY-3189 > URL: https://issues.jboss.org/browse/WFLY-3189 > Project: WildFly > Issue Type: Bug > Components: EJB > Affects Versions: 8.0.0.Final > Environment: WildFly 8.0.0.Final > Reporter: shinzey shinzey > Assignee: David Lloyd > Attachments: p.patch > > > I'm trying to configure code completion for jboss-ejb3.xml with schema, but fail to do that due to the following validation error: > {noformat} > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-beanType' to a(n) 'type definition' component. [33] > src-resolve: Cannot resolve the name 'javaee:jboss-ejb-jarType' to a(n) 'type definition' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-enterprise-beansType' to a(n) 'type definition' component. [37] > src-resolve: Cannot resolve the name 'javaee:assembly-descriptor-entry' to a(n) 'element declaration' component. [35] > src-resolve: Cannot resolve the name 'javaee:jboss-assembly-descriptor-bean-entryType' to a(n) 'type definition' component. [39] > {noformat} > The jboss-ejb3.xml is quite simple: > {code:xml} > <?xml version="1.0" encoding="UTF-8"?> > <jboss:ejb-jar version="3.1" impl-version="2.0" > xmlns="http://java.sun.com/xml/ns/javaee" > xmlns:jboss="http://www.jboss.com/xml/ns/javaee" > xmlns:s="urn:security:1.1" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/ejb-jar_3_1.xsd > http://www.jboss.com/xml/ns/javaee http://www.jboss.org/j2ee/schema/jboss-ejb3-2_0.xsd"> > <assembly-descriptor> > <s:security> > <ejb-name>*</ejb-name> > <s:security-domain>testsd</s:security-domain> > </s:security> > </assembly-descriptor> > </jboss:ejb-jar> > {code} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

10 years, 1 month

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 September 2014