January 2015 - jboss-jira - Jboss List Archives

[JBoss JIRA] (WFLY-4214) Update Maven to latest version 2.3.5

by Tom Jenkinson (JIRA)

Tom Jenkinson created WFLY-4214: ----------------------------------- Summary: Update Maven to latest version 2.3.5 Key: WFLY-4214 URL: https://issues.jboss.org/browse/WFLY-4214 Project: WildFly Issue Type: Component Upgrade Components: Build System Reporter: Tom Jenkinson Assignee: Tom Jenkinson {code} [tom@TOM-PC jboss-as](WFLY-4175)(11:08:43) $ ./tools/download-maven.sh % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 258 100 258 0 0 973 0 --:--:-- --:--:-- --:--:-- 973 Archive: maven.zip End-of-central-directory signature not found. Either this file is not a zipfile, or it constitutes one disk of a multi-part archive. In the latter case the central directory and zipfile comment will be found on the last disk(s) of this archive. unzip: cannot find zipfile directory in maven.zip, and cannot find maven.zip.zip, period. mv: cannot stat `apache-maven*': No such file or directory {code} http://www.apache.org/dist/maven/maven-3/3.2.3/binaries/apache-maven-3.2.... is gone, it is now 3.2.5. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-674?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-674. -------------------------------- Resolution: Rejected If you write 69.99 you're in reality saying that the value is a double with all the rounding issues it implies. Saying explicitly that it is a BigDecimal (writing it as 69.99B) fixes the problem. > Rules with bigdecimal comparison not matched for certain values > --------------------------------------------------------------- > > Key: DROOLS-674 > URL: https://issues.jboss.org/browse/DROOLS-674 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final, 6.2.0.CR3 > Reporter: Joseph Alex > Assignee: Mario Fusco > Priority: Minor > Attachments: BigDecimalTestFragment.java > > > For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached. > The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two. > Envrionment: > Drools : 5.5.0.Final > Java version : Java(TM) SE Runtime Environment (build 1.6.0_21-b06) > OS : CentOS release 6.1 (Final) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-674) Rules with bigdecimal comparison not matched for certain values

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-674?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-674: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Rules with bigdecimal comparison not matched for certain values > --------------------------------------------------------------- > > Key: DROOLS-674 > URL: https://issues.jboss.org/browse/DROOLS-674 > Project: Drools > Issue Type: Bug > Affects Versions: 5.5.0.Final, 6.2.0.CR3 > Reporter: Joseph Alex > Assignee: Mario Fusco > Priority: Minor > Attachments: BigDecimalTestFragment.java > > > For rules which compare BigDecimal inputs against a range considering 2 decimal place precision, match does not happen when the input equals certain upper bounds. Testcase attached. > The rules match when the upper bound is specified with a < condition instead of <= (i.e <70.00 instead of <=69.99) , which seem to indicate value seen by Drools is somewhere between the two. > Envrionment: > Drools : 5.5.0.Final > Java version : Java(TM) SE Runtime Environment (build 1.6.0_21-b06) > OS : CentOS release 6.1 (Final) -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (WFLY-4164) New JTS record types are not showing up in the CLI

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/WFLY-4164?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on WFLY-4164: ----------------------------------------------- Kabir Khan <kkhan(a)redhat.com> changed the Status of [bug 1168973|https://bugzilla.redhat.com/show_bug.cgi?id=1168973] from POST to MODIFIED > New JTS record types are not showing up in the CLI > -------------------------------------------------- > > Key: WFLY-4164 > URL: https://issues.jboss.org/browse/WFLY-4164 > Project: WildFly > Issue Type: Enhancement > Components: CLI, Transactions > Reporter: Tom Jenkinson > Assignee: Michael Musgrove > > We need to expose the new JTS record types in the tooling: > {code} > AssumedCompleteHeuristicTransaction > AssumedCompleteHeuristicServerTransaction > AssumedCompleteTransaction > AssumedCompleteServerTransaction > {code} > We need these because if a transaction ends up in a heuristic state we can't actually view this using the CLI even though the records are in the object store. This has the consequence that a transaction can remain in the object store indefinitely. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-676) Optional SortedMap semantics for matching

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-676?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-676. -------------------------------- Resolution: Done We already have indexes for comparison constraints ( e.g. https://github.com/droolsjbpm/drools/blob/master/drools-core/src/main/jav... ) based on a custom made implementation of a red-black tree. > Optional SortedMap semantics for matching > ----------------------------------------- > > Key: DROOLS-676 > URL: https://issues.jboss.org/browse/DROOLS-676 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.2.0.CR3 > Environment: any > Reporter: Paul Houle > Assignee: Mario Fusco > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Drools uses a Map instead of a SortedMap to accelerate the matching of patterns that have an equality relationship. Performance-wise this is the right decision most of the time, but if one wanted to accelerate matching of patterns such as > Person(age > 100) > having a sorted index could be beneficial. In a case like that the object in question must implement Comparable or be associated with a Comparator. This behavior could be turned on for a particular field with @-annotation in either the DRL or Java file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-676) Optional SortedMap semantics for matching

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-676?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-676: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Optional SortedMap semantics for matching > ----------------------------------------- > > Key: DROOLS-676 > URL: https://issues.jboss.org/browse/DROOLS-676 > Project: Drools > Issue Type: Feature Request > Affects Versions: 6.2.0.CR3 > Environment: any > Reporter: Paul Houle > Assignee: Mario Fusco > Original Estimate: 4 weeks > Remaining Estimate: 4 weeks > > Drools uses a Map instead of a SortedMap to accelerate the matching of patterns that have an equality relationship. Performance-wise this is the right decision most of the time, but if one wanted to accelerate matching of patterns such as > Person(age > 100) > having a sorted index could be beneficial. In a case like that the object in question must implement Comparable or be associated with a Comparator. This behavior could be turned on for a particular field with @-annotation in either the DRL or Java file. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-673) NPE because ConsequenceMetaData.toString is not null-safe

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-673?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-673: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > NPE because ConsequenceMetaData.toString is not null-safe > --------------------------------------------------------- > > Key: DROOLS-673 > URL: https://issues.jboss.org/browse/DROOLS-673 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Reporter: george thomas > Assignee: Mario Fusco > Priority: Minor > Attachments: ConsequenceMetaData.NPE.log > > > The {{toString()}} method in {{org.drools.core.rule.ConsequenceMetaData}} is not null-safe. It assumes that the {{List}} {{statements}} contains at least one element. > This is a problem when the method gets invoked during the serialization-based deep clone effected during initialization under certain conditions (see the "Reproduce" section). > With this combination, code in {{java.io.ObjectOutputStream}} ends up invoking the {{toString()}} method in order to print additional information in the stack trace for {{java.io.NotSerializableException}}. I have attached a snippet of the stack trace as a reference. > The code in question is unchanged even in the [latest version in github|https://github.com/droolsjbpm/drools/blob/master/drools-core/src/m...]. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-673) NPE because ConsequenceMetaData.toString is not null-safe

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-673?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-673. -------------------------------- Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/908d8ca52f85202d2f2014b7d221f... > NPE because ConsequenceMetaData.toString is not null-safe > --------------------------------------------------------- > > Key: DROOLS-673 > URL: https://issues.jboss.org/browse/DROOLS-673 > Project: Drools > Issue Type: Bug > Affects Versions: 6.1.0.Final > Reporter: george thomas > Assignee: Mario Fusco > Priority: Minor > Attachments: ConsequenceMetaData.NPE.log > > > The {{toString()}} method in {{org.drools.core.rule.ConsequenceMetaData}} is not null-safe. It assumes that the {{List}} {{statements}} contains at least one element. > This is a problem when the method gets invoked during the serialization-based deep clone effected during initialization under certain conditions (see the "Reproduce" section). > With this combination, code in {{java.io.ObjectOutputStream}} ends up invoking the {{toString()}} method in order to print additional information in the stack trace for {{java.io.NotSerializableException}}. I have attached a snippet of the stack trace as a reference. > The code in question is unchanged even in the [latest version in github|https://github.com/droolsjbpm/drools/blob/master/drools-core/src/m...]. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-677) Resolve nested classes when parent is imported

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-677?page=com.atlassian.jira.plugin... ] Mario Fusco resolved DROOLS-677. -------------------------------- Resolution: Done Fixed by https://github.com/droolsjbpm/drools/commit/c625aec8a9c8bdf3ee358115686d1... > Resolve nested classes when parent is imported > ---------------------------------------------- > > Key: DROOLS-677 > URL: https://issues.jboss.org/browse/DROOLS-677 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR3 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Minor > Fix For: 6.2.0.Final > > > Inner classes are not resolved correctly if qualified using their parent class: > {code} > import Outer; > declare Bean > field : Outer.Inner // an inner class of Outer > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (DROOLS-677) Resolve nested classes when parent is imported

by Mario Fusco (JIRA)

[ https://issues.jboss.org/browse/DROOLS-677?page=com.atlassian.jira.plugin... ] Mario Fusco reassigned DROOLS-677: ---------------------------------- Assignee: Mario Fusco (was: Mark Proctor) > Resolve nested classes when parent is imported > ---------------------------------------------- > > Key: DROOLS-677 > URL: https://issues.jboss.org/browse/DROOLS-677 > Project: Drools > Issue Type: Bug > Affects Versions: 6.2.0.CR3 > Reporter: Davide Sottara > Assignee: Mario Fusco > Priority: Minor > Fix For: 6.2.0.Final > > > Inner classes are not resolved correctly if qualified using their parent class: > {code} > import Outer; > declare Bean > field : Outer.Inner // an inner class of Outer > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

9 years, 4 months

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 January 2015