October 2013 - jboss-jira - Jboss List Archives

[JBoss JIRA] (DROOLS-115) Add support for strong negation

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-115?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-115: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Add support for strong negation > ------------------------------- > > Key: DROOLS-115 > URL: https://issues.jboss.org/browse/DROOLS-115 > Project: Drools > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Davide Sottara > Assignee: Davide Sottara > Priority: Minor > Fix For: 6.0.0.CR5 > > > Drools "not" operator implements a type of "negation by failure", i.e. not X() behaves as the negation of "exists" or, in other words, translates as "it is NOT asserted that ...". > However, another form of stronger negation is needed to express conditionals such as "it is asserted that NOT ..." > It should be possible, then, to assert facts both in a "positive" and "negative" way, to assert THAT and THAT NOT. > The language should also support a "neg" CE to create "negative" patterns which will match with negative facts. I.e. it should be possible to write rules such as: > when $p : Person() and Car( owner == $p ) then > // a positive, matching Car is present in the WM > when $p : Person() and neg Car( owner == $p ) then > // a negative, matching Car is present in the WM > when $p : Person() and not Car( owner == $p ) then > // neither a positive nor a negative fact exists in the WM > For a more detailed description and motivation see e.g.: > https://oxygen.informatik.tu-cottbus.de/publications/wagner/WebRules2Neg.pdf -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-257) Past events beyond expiration are not expired

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-257?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-257: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Past events beyond expiration are not expired > --------------------------------------------- > > Key: DROOLS-257 > URL: https://issues.jboss.org/browse/DROOLS-257 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR3 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-254) "Exists OR" rules are compiled inconsistently

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-254?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-254: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > "Exists OR" rules are compiled inconsistently > --------------------------------------------- > > Key: DROOLS-254 > URL: https://issues.jboss.org/browse/DROOLS-254 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR3 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Critical > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > Exists ( A or B ) is transformed into ( Exists A ) or ( Exists B ) > In case both A and B are asserted, they result in two activations, > whereas one would expect only one. > Moreover, the equivalent not ( (not A) and (not B) ) results in only > one activation. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-251) Classloader fails to resolve when annotation and declared class have the same name

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-251?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-251: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Classloader fails to resolve when annotation and declared class have the same name > ---------------------------------------------------------------------------------- > > Key: DROOLS-251 > URL: https://issues.jboss.org/browse/DROOLS-251 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR2 > Reporter: Davide Sottara > Assignee: Mark Proctor > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > package test > declare Annot > fld : int @Annot > end > The packagebuilder type resolver will confuse the annotation with the declared class and throw exceptions (varies depending on optional import > statements) -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-249) Handle conflicts when using @position in declared types

by Michael Biarnes Kiefer (JIRA)

[ https://issues.jboss.org/browse/DROOLS-249?page=com.atlassian.jira.plugin... ] Michael Biarnes Kiefer updated DROOLS-249: ------------------------------------------ Fix Version/s: 6.0.0.CR5 (was: 6.0.0.CR4) > Handle conflicts when using @position in declared types > ------------------------------------------------------- > > Key: DROOLS-249 > URL: https://issues.jboss.org/browse/DROOLS-249 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR2 > Reporter: Davide Sottara > Assignee: Mark Proctor > Priority: Minor > Fix For: 5.5.1.Final, 6.0.0.CR5 > > > declare A > f : int @position(2) > g : int @position(1) > end > declare B extends A > h : int @position(3) > i : int @position(2) > end > The resulting field order may not be deterministic because of > - the clashes (2) > - the missing pos (0) > this is dangerous when used with positional constraints > B( $x, $y, $z, $w ; ) > Marked as minor because of the obvious workaround -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-268) Delayed rule schedules are computed erroneously

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-268?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-268. -------------------------------- Fix Version/s: 5.5.1.Final Resolution: Done > Delayed rule schedules are computed erroneously > ----------------------------------------------- > > Key: DROOLS-268 > URL: https://issues.jboss.org/browse/DROOLS-268 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR3 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 5.5.1.Final, 6.0.0.Final > > > Consider the following case, where all patterns are events > $a : A() > $b : B() > not C( this after[0,N] $a ) > When the schedule time is computed, the ACTIVATION timestamp is considered > as the starting timestamp, rather than $a's timestamp. > If $b is insert after $a, the rule's schedule will be N time units after $b. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-268) Delayed rule schedules are computed erroneously

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-268?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-268: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Delayed rule schedules are computed erroneously > ----------------------------------------------- > > Key: DROOLS-268 > URL: https://issues.jboss.org/browse/DROOLS-268 > Project: Drools > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 5.5.0.Final, 6.0.0.CR3 > Reporter: Davide Sottara > Assignee: Mario Fusco > Fix For: 6.0.0.Final > > > Consider the following case, where all patterns are events > $a : A() > $b : B() > not C( this after[0,N] $a ) > When the schedule time is computed, the ACTIVATION timestamp is considered > as the starting timestamp, rather than $a's timestamp. > If $b is insert after $a, the rule's schedule will be N time units after $b. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-207) Inconsistent Stack Map when inserting throw Expression with Java 7

by Aftab Khan (JIRA)

[ https://issues.jboss.org/browse/JASSIST-207?page=com.atlassian.jira.plugi... ] Aftab Khan commented on JASSIST-207: ------------------------------------ Hi Shigeru, I am facing the same issue in javassist-3.18.1-GA . I have attached the class file for reference The error message i am getting is: Caused by: java.lang.VerifyError: Expecting a stackmap frame at branch target 416 in method com.emeter.activitygwy.transport.AGDelegateImpl.processWorkResponseMessage$Impl(Lcom/emeter/activitygwy/xsd/activitygwy/gen/WorkResponseMessageDocument;)V at offset 379 at java.lang.Class.getDeclaredConstructors0(Native Method) at java.lang.Class.privateGetDeclaredConstructors(Class.java:2404) at java.lang.Class.getDeclaredConstructors(Class.java:1853) at org.springframework.beans.factory.annotation.AutowiredAnnotationBeanPostProcessor.determineCandidateConstructors(AutowiredAnnotationBeanPostProcessor.java:229) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.determineConstructorsFromBeanPostProcessors(AbstractAutowireCapableBeanFactory.java:962) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:935) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456) at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:294) at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:225) at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:291) at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:193) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322) at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.applyPropertyValues(AbstractAutowireCapableBeanFactory.java:1360) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.populateBean(AbstractAutowireCapableBeanFactory.java:1118) at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:517) ... 25 more Please help regarding the same. Regards, Aftab > Inconsistent Stack Map when inserting throw Expression with Java 7 > ------------------------------------------------------------------ > > Key: JASSIST-207 > URL: https://issues.jboss.org/browse/JASSIST-207 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.18.0-GA > Reporter: Ben Romberg > Assignee: Shigeru Chiba > Priority: Critical > Fix For: 3.18.1-GA, 3.19.0-GA > > Attachments: afterInsertThrowExpression.txt, AGDelegateImpl.class, beforeInsertThrowExpression.txt, conditionalThrowExceptionInserted.txt > > > I wrote a unit-test for javassist, reproducing the issue: > {code} > public class ThrowExpressionCorruptsStackMapTableTest extends JvstTestRoot { > public ThrowExpressionCorruptsStackMapTableTest(String name) { > super(name); > } > public void testInsertLocalVars() throws Exception { > CtClass cc = sloader.get("test4.LocalVars"); > CtMethod m1 = cc.getDeclaredMethod("run"); > m1.insertBefore("throw new AssertionError((Object) \"assertion error\");"); > cc.writeFile(); > Object obj = make(cc.getName()); > assertEquals(10, invoke(obj, "run")); > } > } > {code} > Throws: > java.lang.VerifyError: Expecting a stack map frame in method test4.LocalVars.run()I at offset 45 > My use-case is almost the same, inserting a "throw AssertionError(...)" expression with insertBefore. However, I get a slightly different error message: > Stack map does not match the one at exception handler 37 in method timeofday.TimeOfDay.getSecond()I at offset 27 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JASSIST-207) Inconsistent Stack Map when inserting throw Expression with Java 7

by Aftab Khan (JIRA)

[ https://issues.jboss.org/browse/JASSIST-207?page=com.atlassian.jira.plugi... ] Aftab Khan updated JASSIST-207: ------------------------------- Attachment: AGDelegateImpl.class > Inconsistent Stack Map when inserting throw Expression with Java 7 > ------------------------------------------------------------------ > > Key: JASSIST-207 > URL: https://issues.jboss.org/browse/JASSIST-207 > Project: Javassist > Issue Type: Bug > Affects Versions: 3.18.0-GA > Reporter: Ben Romberg > Assignee: Shigeru Chiba > Priority: Critical > Fix For: 3.18.1-GA, 3.19.0-GA > > Attachments: afterInsertThrowExpression.txt, AGDelegateImpl.class, beforeInsertThrowExpression.txt, conditionalThrowExceptionInserted.txt > > > I wrote a unit-test for javassist, reproducing the issue: > {code} > public class ThrowExpressionCorruptsStackMapTableTest extends JvstTestRoot { > public ThrowExpressionCorruptsStackMapTableTest(String name) { > super(name); > } > public void testInsertLocalVars() throws Exception { > CtClass cc = sloader.get("test4.LocalVars"); > CtMethod m1 = cc.getDeclaredMethod("run"); > m1.insertBefore("throw new AssertionError((Object) \"assertion error\");"); > cc.writeFile(); > Object obj = make(cc.getName()); > assertEquals(10, invoke(obj, "run")); > } > } > {code} > Throws: > java.lang.VerifyError: Expecting a stack map frame in method test4.LocalVars.run()I at offset 45 > My use-case is almost the same, inserting a "throw AssertionError(...)" expression with insertBefore. However, I get a slightly different error message: > Stack map does not match the one at exception handler 37 in method timeofday.TimeOfDay.getSecond()I at offset 27 -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (WFLY-1507) Investigate failure in StatefulWithXPCFailoverTestCase

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-1507?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-1507: ----------------------------------------------- Richard Janík <rjanik(a)redhat.com> changed the Status of [bug 963610|https://bugzilla.redhat.com/show_bug.cgi?id=963610] from ON_QA to ASSIGNED > Investigate failure in StatefulWithXPCFailoverTestCase > ------------------------------------------------------ > > Key: WFLY-1507 > URL: https://issues.jboss.org/browse/WFLY-1507 > Project: WildFly > Issue Type: Bug > Reporter: jaikiran pai > Assignee: Paul Ferraro > Priority: Blocker > Fix For: 8.0.0.Alpha2 > > Attachments: log2.txt > > > Numerous exceptions are reported and the tests fails intermittently but often in StatefulWithXPCFailoverTestCase. > Entire logs attached. -- 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, 7 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 October 2013