September 2012 - jboss-jira - Jboss List Archives

[JBoss JIRA] (JBRULES-3334) AbstractTabuAcceptor doesn't add the starting solution as tabu

by Patrik Dufresne (Created) (JIRA)

AbstractTabuAcceptor doesn't add the starting solution as tabu -------------------------------------------------------------- Key: JBRULES-3334 URL: https://issues.jboss.org/browse/JBRULES-3334 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-planner Affects Versions: 5.3.1.Final Reporter: Patrik Dufresne Assignee: Mark Proctor When setting a complete solution tabu, the starting solution is not considered a Tabu making it possible to visit the same solution again. Consider a situation where there is construction phase followed by a local search phase. The construction phase will create a solution that will not be added to the tabu list of the local search phased. To fix it, I suggest to override the function phaseStarted(...) in SolutionTabuAcceptor to add solution to the Tabu map. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

9
10
0 / 0

[JBoss JIRA] (JBRULES-3324) Refactor the Simulation Fluents for World Remoting

by Mark Proctor (Created) (JIRA)

Refactor the Simulation Fluents for World Remoting -------------------------------------------------- Key: JBRULES-3324 URL: https://issues.jboss.org/browse/JBRULES-3324 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Mark Proctor Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (JBRULES-3607) Drools Grid-Node issue

by Sunny Osaje (JIRA)

Sunny Osaje created JBRULES-3607: ------------------------------------ Summary: Drools Grid-Node issue Key: JBRULES-3607 URL: https://issues.jboss.org/browse/JBRULES-3607 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Reporter: Sunny Osaje Assignee: Mark Proctor -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
5
0 / 0

[JBoss JIRA] (JBRULES-3578) Normalize tuple interfaces eliminating the separate interface for RightTuples

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3578: -------------------------------------- Summary: Normalize tuple interfaces eliminating the separate interface for RightTuples Key: JBRULES-3578 URL: https://issues.jboss.org/browse/JBRULES-3578 Project: Drools Issue Type: Sub-task Security Level: Public (Everyone can see) Components: drools-compiler, drools-core Affects Versions: 5.4.0.Final Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.5.0.Beta1 The current split of tuples into LeftTuples and RightTuples adds complexity to the system and makes impossible for the system to join (concatenate) 2 left tuples. The goal of this task is to normalize all tuple interfaces into a single interface, allowing two-input nodes like joins to join 2 tuples, independently of the number of elements in each. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

2
2
0 / 0

[JBoss JIRA] (JBRULES-3448) XLS Decision tables: Add support for Condition column DRL fragments

by Michael Anstis (JIRA)

Michael Anstis created JBRULES-3448: --------------------------------------- Summary: XLS Decision tables: Add support for Condition column DRL fragments Key: JBRULES-3448 URL: https://issues.jboss.org/browse/JBRULES-3448 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Michael Anstis Assignee: Michael Anstis Fix For: 5.5.0.Beta1 Condition columns in XLS Decision Tables have a row for Object type and a row for code "snippet". The code snippet is taken as predicates within the Object type; for example:- {code} CONDITION | CONDITION ---------------------------- MyFact ---------------------------- field1 == | field2 == ---------------------------- a | b {code} This is rather limiting (and certainly not conducive to decision table round-tripping). Ideally we need to support:- {code} CONDITION ---------------------------------------------- MyFact( field1 == $param1, field2 == $param2 ) ---------------------------------------------- ---------------------------------------------- a,b {code} Even more ideally it'd be good to be able to register "column handlers" so this can be extended easily. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

1
3
0 / 0

[JBoss JIRA] (JBRULES-3514) Add support to event sequencing

by Edson Tirelli (JIRA)

Edson Tirelli created JBRULES-3514: -------------------------------------- Summary: Add support to event sequencing Key: JBRULES-3514 URL: https://issues.jboss.org/browse/JBRULES-3514 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-api, drools-compiler, drools-core Reporter: Edson Tirelli Assignee: Edson Tirelli Fix For: 5.5.0.Beta1 The purpose of this ticket is to centralize the discussions regarding the implementation of event sequencing as detailed in the wiki page at: https://community.jboss.org/wiki/EventSequencing The highlevel discussions can be added to this ticket while individual sub-tickets will be created for the implementation of each sub-feature. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

4
28
0 / 0

[JBoss JIRA] (JBRULES-3637) The "from" CE does not manage @events correctly

by Davide Sottara (JIRA)

Davide Sottara created JBRULES-3637: --------------------------------------- Summary: The "from" CE does not manage @events correctly Key: JBRULES-3637 URL: https://issues.jboss.org/browse/JBRULES-3637 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-core (fusion) Affects Versions: 5.4.0.Final Reporter: Davide Sottara Assignee: Edson Tirelli Priority: Critical Fix For: 5.5.0.Beta1 If an event type (i.e. an instance of a class marked with @role(event)) is returned by a "from" node, it is not wrapped by an EventFactHandle as expected, so e.g. any attempt to use temporal operators will fail. See the test case below for an example The problem is in FromNode.java around line 200, where the new handles are created without passing an ObjectTypeConfiguration, leading to the default creation of a DefaultFactHandle. I wonder if it's possible to simply retrieve the ObjectTypeConf: workingMemory.getObjectTypeConfigurationRegistry().getObjectTypeConf( context.getEntryPoint(), object ) and pass it to the handle factory method. I tested it and it works for the test case below, but there may be other side-effects I'm not seeing. --------------------------------------------------------------------------- May be related (but not the same as) #JBRULES-2423 -- 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

13 years, 8 months

4
7
0 / 0

[JBoss JIRA] (AS7-4075) Upgrade commons-pool to 1.6

by Julio Pires (JIRA)

Julio Pires created AS7-4075: -------------------------------- Summary: Upgrade commons-pool to 1.6 Key: AS7-4075 URL: https://issues.jboss.org/browse/AS7-4075 Project: Application Server 7 Issue Type: Library Upgrade Reporter: Julio Pires JBoss 7 contains version 1.5.6. The version 1.6 contains bugs fixed and improvements. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
10
0 / 0

[JBoss JIRA] (AS7-5400) Core model testing infrastrucutre

by Tomaz Cerar (JIRA)

Tomaz Cerar created AS7-5400: -------------------------------- Summary: Core model testing infrastrucutre Key: AS7-5400 URL: https://issues.jboss.org/browse/AS7-5400 Project: Application Server 7 Issue Type: Task Components: Test Suite Reporter: Tomaz Cerar Assignee: Kabir Khan We extensively test subsystems for model definitions but we do not do such thing for core model. We should have some mechanism to test it and it should cover mostly the same stuff we test now in subsystem tests. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 8 months

3
3
0 / 0

[JBoss JIRA] (JGRP-1517) RELAY2: provide FIFO ordering for relayed messages

by Bela Ban (JIRA)

Bela Ban created JGRP-1517: ------------------------------ Summary: RELAY2: provide FIFO ordering for relayed messages Key: JGRP-1517 URL: https://issues.jboss.org/browse/JGRP-1517 Project: JGroups Issue Type: Feature Request Reporter: Bela Ban Assignee: Bela Ban When relaying messages between (1) a local member and local coordinator (SiteMaster) and (2) between the SiteMaster of one site and the SiteMaster of a remote site, messages are by default FIFO-ordered as we're sending them on a JGroups channel. However, when the target (coordinator or remote SiteMaster) changes, we need to replay unacked messages. If new messages are sent in parallel to the resending of unacked messages, ordering is undefined. Investigate whether (a) ordering is needed (main consumer is Infinispan, so this is certainly not necessary for async repl, but may be needed for sync repl) and (b) how this should get implemented. Re (b): perhaps we can copy the queueing design from SEQUENCER (refactor the code into a separate class, used by both SEQUENCER and FORWARD_TO_COORD). -- 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

13 years, 8 months

1
3
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 September 2012