January 2014 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-418) MVEL Unable to resolve method exception on fact update

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-418?page=com.atlassian.jira.plugin... ] Davide Sottara edited comment on DROOLS-418 at 1/29/14 8:55 PM: ---------------------------------------------------------------- I have just realized that "type == LOW" must be a constraint in a different rule from the one you posted.. That is the one generated from the DT, but I guess you have other rules in your KB: the exception stack trace shows an accumulate being involved. Could you please post the full DRL you are using? Thanks Davide was (Author: dsotty): I have just realized that "type == LOW" must be a constraint in a different rule from the one you posted.. That is the one generated from the DT, but do you have other rules in your KB? > MVEL Unable to resolve method exception on fact update > ------------------------------------------------------ > > Key: DROOLS-418 > URL: https://issues.jboss.org/browse/DROOLS-418 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Linux Mint 15 > Jboss 5.1 > Reporter: Nedo Nedic > Assignee: Mark Proctor > Attachments: Classifier.xls > > > The following rule will fail with an exception after update is called on a fact: > rule "Classifier" > no-loop true > salience 65430 > when > $sn:Snort(sig_priority == "1", type == null) > then > $sn.setType("LOW"); > update($sn); > end > Snort fact type declaration: > declare Snort > @role( event ) > @timestamp( event_date ) > @expires( 1h ) > dport: String > data: String > sport: String > hostname: String > type: String > sig_priority: String > sensor: String > id: java.lang.Long > sig_class_name: String > ip_dst: String > sig_name: String > event_date: java.util.Date > ip_src: String > end > [Error: unable to resolve method: java.util.ArrayList.type() [arglength=0]] > [Near : {... type == "LOW" ....}] > ^ > [Line: 1, Column: 1] > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1071) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:980) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanProperty(ReflectiveAccessorOptimizer.java:670) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanPropertyAO(ReflectiveAccessorOptimizer.java:465) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:370) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:140) > at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159) > at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115) > at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:114) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.MVEL.executeExpression(MVEL.java:930) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:73) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:52) > at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:218) > at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:175) > at org.drools.reteoo.AccumulateNode.evaluateResultConstraints(AccumulateNode.java:655) > at org.drools.reteoo.ReteooWorkingMemory$EvaluateResultConstraints.execute(ReteooWorkingMemory.java:594) > at org.drools.common.PropagationContextImpl.evaluateActionQueue(PropagationContextImpl.java:364) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:371) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:327) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:950) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:894) > at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:269) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-418) MVEL Unable to resolve method exception on fact update

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-418?page=com.atlassian.jira.plugin... ] Davide Sottara edited comment on DROOLS-418 at 1/29/14 8:51 PM: ---------------------------------------------------------------- I have just realized that "type == LOW" must be a constraint in a different rule from the one you posted.. That is the one generated from the DT, but do you have other rules in your KB? was (Author: dsotty): I have just realized that "type == LOW" must be a constraint in a different rule from the one you posted.. I'll run the decision table and get back to you > MVEL Unable to resolve method exception on fact update > ------------------------------------------------------ > > Key: DROOLS-418 > URL: https://issues.jboss.org/browse/DROOLS-418 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Linux Mint 15 > Jboss 5.1 > Reporter: Nedo Nedic > Assignee: Mark Proctor > Attachments: Classifier.xls > > > The following rule will fail with an exception after update is called on a fact: > rule "Classifier" > no-loop true > salience 65430 > when > $sn:Snort(sig_priority == "1", type == null) > then > $sn.setType("LOW"); > update($sn); > end > Snort fact type declaration: > declare Snort > @role( event ) > @timestamp( event_date ) > @expires( 1h ) > dport: String > data: String > sport: String > hostname: String > type: String > sig_priority: String > sensor: String > id: java.lang.Long > sig_class_name: String > ip_dst: String > sig_name: String > event_date: java.util.Date > ip_src: String > end > [Error: unable to resolve method: java.util.ArrayList.type() [arglength=0]] > [Near : {... type == "LOW" ....}] > ^ > [Line: 1, Column: 1] > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1071) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:980) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanProperty(ReflectiveAccessorOptimizer.java:670) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanPropertyAO(ReflectiveAccessorOptimizer.java:465) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:370) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:140) > at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159) > at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115) > at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:114) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.MVEL.executeExpression(MVEL.java:930) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:73) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:52) > at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:218) > at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:175) > at org.drools.reteoo.AccumulateNode.evaluateResultConstraints(AccumulateNode.java:655) > at org.drools.reteoo.ReteooWorkingMemory$EvaluateResultConstraints.execute(ReteooWorkingMemory.java:594) > at org.drools.common.PropagationContextImpl.evaluateActionQueue(PropagationContextImpl.java:364) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:371) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:327) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:950) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:894) > at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:269) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-418) MVEL Unable to resolve method exception on fact update

by Davide Sottara (JIRA)

[ https://issues.jboss.org/browse/DROOLS-418?page=com.atlassian.jira.plugin... ] Davide Sottara commented on DROOLS-418: --------------------------------------- I have just realized that "type == LOW" must be a constraint in a different rule from the one you posted.. I'll run the decision table and get back to you > MVEL Unable to resolve method exception on fact update > ------------------------------------------------------ > > Key: DROOLS-418 > URL: https://issues.jboss.org/browse/DROOLS-418 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final > Environment: Linux Mint 15 > Jboss 5.1 > Reporter: Nedo Nedic > Assignee: Mark Proctor > Attachments: Classifier.xls > > > The following rule will fail with an exception after update is called on a fact: > rule "Classifier" > no-loop true > salience 65430 > when > $sn:Snort(sig_priority == "1", type == null) > then > $sn.setType("LOW"); > update($sn); > end > Snort fact type declaration: > declare Snort > @role( event ) > @timestamp( event_date ) > @expires( 1h ) > dport: String > data: String > sport: String > hostname: String > type: String > sig_priority: String > sensor: String > id: java.lang.Long > sig_class_name: String > ip_dst: String > sig_name: String > event_date: java.util.Date > ip_src: String > end > [Error: unable to resolve method: java.util.ArrayList.type() [arglength=0]] > [Near : {... type == "LOW" ....}] > ^ > [Line: 1, Column: 1] > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:1071) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getMethod(ReflectiveAccessorOptimizer.java:980) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanProperty(ReflectiveAccessorOptimizer.java:670) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.getBeanPropertyAO(ReflectiveAccessorOptimizer.java:465) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.compileGetChain(ReflectiveAccessorOptimizer.java:370) > at org.mvel2.optimizers.impl.refl.ReflectiveAccessorOptimizer.optimizeAccessor(ReflectiveAccessorOptimizer.java:140) > at org.mvel2.ast.ASTNode.optimize(ASTNode.java:159) > at org.mvel2.ast.ASTNode.getReducedValueAccelerated(ASTNode.java:115) > at org.mvel2.ast.BinaryOperation.getReducedValueAccelerated(BinaryOperation.java:114) > at org.mvel2.MVELRuntime.execute(MVELRuntime.java:86) > at org.mvel2.compiler.CompiledExpression.getDirectValue(CompiledExpression.java:123) > at org.mvel2.compiler.CompiledExpression.getValue(CompiledExpression.java:119) > at org.mvel2.MVEL.executeExpression(MVEL.java:930) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:73) > at org.drools.rule.constraint.MvelConditionEvaluator.evaluate(MvelConditionEvaluator.java:52) > at org.drools.rule.constraint.MvelConstraint.evaluate(MvelConstraint.java:218) > at org.drools.rule.constraint.MvelConstraint.isAllowed(MvelConstraint.java:175) > at org.drools.reteoo.AccumulateNode.evaluateResultConstraints(AccumulateNode.java:655) > at org.drools.reteoo.ReteooWorkingMemory$EvaluateResultConstraints.execute(ReteooWorkingMemory.java:594) > at org.drools.common.PropagationContextImpl.evaluateActionQueue(PropagationContextImpl.java:364) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:371) > at org.drools.common.NamedEntryPoint.insert(NamedEntryPoint.java:327) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:950) > at org.drools.common.AbstractWorkingMemory.insert(AbstractWorkingMemory.java:894) > at org.drools.impl.StatefulKnowledgeSessionImpl.insert(StatefulKnowledgeSessionImpl.java:269) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2694) CLI example output for connecting to domain controller inaccurate

by Tom Wells (JIRA)

[ https://issues.jboss.org/browse/WFLY-2694?page=com.atlassian.jira.plugin.... ] Tom Wells closed WFLY-2694. --------------------------- > CLI example output for connecting to domain controller inaccurate > ----------------------------------------------------------------- > > Key: WFLY-2694 > URL: https://issues.jboss.org/browse/WFLY-2694 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.CR1 > Environment: Raspberry Pi > Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux > Reporter: Mark Little > Assignee: Tom Wells > Priority: Minor > Fix For: 8.0.0.Final > > > According to https://docs.jboss.org/author/display/WFLY8/Management+Clients > --- > ./bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server > or 'help' for the list of supported commands. > [disconnected /] > > [disconnected /] connect > Connected to domain controller at localhost:9999 > ---- > But no "Connected to domain controller" is output. No indication of success is given other than the next line of the CLI has the hostname (localhost) referenced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2694) CLI example output for connecting to domain controller inaccurate

by Tom Wells (JIRA)

[ https://issues.jboss.org/browse/WFLY-2694?page=com.atlassian.jira.plugin.... ] Tom Wells resolved WFLY-2694. ----------------------------- Fix Version/s: 8.0.0.Final Resolution: Done Corrected the CLI output documented in the following section: https://docs.jboss.org/author/display/WFLY8/Management+Clients > CLI example output for connecting to domain controller inaccurate > ----------------------------------------------------------------- > > Key: WFLY-2694 > URL: https://issues.jboss.org/browse/WFLY-2694 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Documentation > Affects Versions: 8.0.0.CR1 > Environment: Raspberry Pi > Linux raspberrypi 3.2.27+ #250 PREEMPT Thu Oct 18 19:03:02 BST 2012 armv6l GNU/Linux > Reporter: Mark Little > Assignee: Tom Wells > Priority: Minor > Fix For: 8.0.0.Final > > > According to https://docs.jboss.org/author/display/WFLY8/Management+Clients > --- > ./bin/jboss-cli.sh > You are disconnected at the moment. Type 'connect' to connect to the server > or 'help' for the list of supported commands. > [disconnected /] > > [disconnected /] connect > Connected to domain controller at localhost:9999 > ---- > But no "Connected to domain controller" is output. No indication of success is given other than the next line of the CLI has the hostname (localhost) referenced. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2819) Cherry-pick Mojarra fix for ClassPathException when custom VisitContextFactory is used

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-2819?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-2819: ----------------------------- Affects Version/s: 8.0.0.CR1 (was: 8.0.0.Final) > Cherry-pick Mojarra fix for ClassPathException when custom VisitContextFactory is used > -------------------------------------------------------------------------------------- > > Key: WFLY-2819 > URL: https://issues.jboss.org/browse/WFLY-2819 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.CR1 > Reporter: Lukáš Fryč > Assignee: Farah Juma > > See https://java.net/jira/browse/JAVASERVERFACES-3156 > This fix allows to leverage VisitContextFactory/Wrapper features properly and enables RF-13505. > See also related update: WFLY-2796 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2819) Cherry-pick Mojarra fix for ClassPathException when custom VisitContextFactory is used

by Farah Juma (JIRA)

[ https://issues.jboss.org/browse/WFLY-2819?page=com.atlassian.jira.plugin.... ] Farah Juma updated WFLY-2819: ----------------------------- Fix Version/s: 8.0.0.Final > Cherry-pick Mojarra fix for ClassPathException when custom VisitContextFactory is used > -------------------------------------------------------------------------------------- > > Key: WFLY-2819 > URL: https://issues.jboss.org/browse/WFLY-2819 > Project: WildFly > Issue Type: Component Upgrade > Security Level: Public(Everyone can see) > Components: JSF > Affects Versions: 8.0.0.CR1 > Reporter: Lukáš Fryč > Assignee: Farah Juma > Fix For: 8.0.0.Final > > > See https://java.net/jira/browse/JAVASERVERFACES-3156 > This fix allows to leverage VisitContextFactory/Wrapper features properly and enables RF-13505. > See also related update: WFLY-2796 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2322) Update add-user to REJECT bad passwords

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2322?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-2322: ------------------------------------ actually whats wrong me with. Why do we want to reject bad passwords by default. Isn't a warning enough? > Update add-user to REJECT bad passwords > --------------------------------------- > > Key: WFLY-2322 > URL: https://issues.jboss.org/browse/WFLY-2322 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scripts > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 8.0.0.Final > > > Before we release .Final add-user.sh should be switched back to rejecting bad passwords rather than just warning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2322) Update add-user to REJECT bad passwords

by Jason Greene (JIRA)

[ https://issues.jboss.org/browse/WFLY-2322?page=com.atlassian.jira.plugin.... ] Jason Greene commented on WFLY-2322: ------------------------------------ btw sorry that i did not correctly parse the subject of this issue and you put in the work > Update add-user to REJECT bad passwords > --------------------------------------- > > Key: WFLY-2322 > URL: https://issues.jboss.org/browse/WFLY-2322 > Project: WildFly > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Scripts > Reporter: Darran Lofthouse > Assignee: Darran Lofthouse > Priority: Blocker > Fix For: 8.0.0.Final > > > Before we release .Final add-user.sh should be switched back to rejecting bad passwords rather than just warning. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (WFLY-2816) Favour jboss-persistence.xml if present

by Scott Marlow (JIRA)

[ https://issues.jboss.org/browse/WFLY-2816?page=com.atlassian.jira.plugin.... ] Scott Marlow updated WFLY-2816: ------------------------------- Forum Reference: http://lists.jboss.org/pipermail/wildfly-dev/2014-January/001522.html > Favour jboss-persistence.xml if present > --------------------------------------- > > Key: WFLY-2816 > URL: https://issues.jboss.org/browse/WFLY-2816 > Project: WildFly > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: JPA / Hibernate, Server > Reporter: Christopher Klein > Assignee: Scott Marlow > Priority: Minor > > For developing for different target application servers (e.g. JBoss and WebSphere) it would be nice if WildFly favours a jboss-persistence.xml instead of the original persistence.xml. > The jboss-persistence.xml is specific for the deployment inside WildFly, the persistence.xml would be the fallback/default for other application servers. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 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 January 2014