February 2011 - jboss-jira - Jboss List Archives

[JBoss JIRA] Created: (JBRULES-1990) Drools workbench should ignore files in derived folders

by Benjamin Papez (JIRA)

Drools workbench should ignore files in derived folders ------------------------------------------------------- Key: JBRULES-1990 URL: https://jira.jboss.org/jira/browse/JBRULES-1990 Project: JBoss Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse Affects Versions: 4.0.7 Reporter: Benjamin Papez Assignee: Mark Proctor In my Eclipse projects (based on maven) I am tagging the target folder as Derived (via right mouse click on folder -> Properties). Eclipse is then not running the validators on that folder, but Drools does. So all the errors are reported twice. Please ignore the copies in Derived folders when doing validation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-1972) Show DRL for decision tables

by Simon Spielmann (JIRA)

Show DRL for decision tables ---------------------------- Key: JBRULES-1972 URL: https://jira.jboss.org/jira/browse/JBRULES-1972 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-eclipse Reporter: Simon Spielmann Assignee: Mark Proctor Sometimes it is very useful to see the generated drl for a decision table. Without it you can't even set breakpoints. I suggest to add a menu item e.g. "show drl" to the context menu for a spreadsheet file in the eclipse ide. I think this shouldn't be to hard to implement. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBRULES-2864) Cannot Set Wait for Completion Property in Property Editor

by Steve Yokanovich (JIRA)

Cannot Set Wait for Completion Property in Property Editor ---------------------------------------------------------- Key: JBRULES-2864 URL: https://issues.jboss.org/browse/JBRULES-2864 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: drools-eclipse (flow) Affects Versions: 5.1.1.FINAL Environment: Linux x86_64 Reporter: Steve Yokanovich Assignee: Mark Proctor When you set the Wait for Completion property of a Human Task to false in the Drools Flow Editor and save the file, there is no change to the resulting BPMN file. If you close the file and reopen it in the editor the property reverts to true. This is also the case in any custom service tasks. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2586) ForEach Node does not work correctly with incorparated subflow nodes

by Grégoire Botquin (JIRA)

ForEach Node does not work correctly with incorparated subflow nodes -------------------------------------------------------------------- Key: JBRULES-2586 URL: https://jira.jboss.org/browse/JBRULES-2586 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.0.1.FINAL Environment: Windows7 Reporter: Grégoire Botquin Assignee: Mark Proctor A ForEach node should process sequentially all elements inside the collection it has to iterate on. This works fine unless there is a SubFlow node incorparted in the ForEachNode. In this case, the messages are not processed sequentially anymore. It looks like that the subflow starts/continue only when the ForEach has terminated its loop. Note : The problem happens when the subflow has a RuleFlowGroup node. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2327) Possibility to map a result to a property bean

by Julien Cheype (JIRA)

Possibility to map a result to a property bean ---------------------------------------------- Key: JBRULES-2327 URL: https://jira.jboss.org/jira/browse/JBRULES-2327 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-core Affects Versions: 5.1.0.M1, 5.0.1.FINAL Reporter: Julien Cheype Assignee: Mark Proctor Be able to map a result to a property bean directly For exemple if I have a bean "Person" with a property String name it could be useful to map it in the result mapping like this: <mapping type="out" from="name" to="test.name" /> -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBRULES-2300) SingleSessionCommandService revisited: facyHandle is null while insert it in a stateful session

by Francesco Chiarelli (JIRA)

SingleSessionCommandService revisited: facyHandle is null while insert it in a stateful session ----------------------------------------------------------------------------------------------- Key: JBRULES-2300 URL: https://jira.jboss.org/jira/browse/JBRULES-2300 Project: Drools Issue Type: Patch Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.0.M1 Environment: jre 1.5 - jboss 5.0.1.GA - Eclipse with jbossTools Reporter: Francesco Chiarelli Assignee: Mark Proctor Priority: Blocker I had need to implement a new SingleSessionCommandService (logical mirror of the original unless registerRollbackSync (), which is no longer invoked and JoinTransaction). The primary thread creates statefulKnowledgeSession via JPA (JTA). The secondary thread load the session, insert facts, fire rules, startProcess, and dispose. In @PreUpdate on SessionInfo, when you create the same snapshot is retrieved correctly, during the insertion of a fact, I get a NPE on org.drools.reteoo.ReteooWorkingMemory at 245: factHandle is null. In debugging I verified that the method throws the exception FromNode.evaluateAndPropagate captured by the command. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
5
0 / 0

[JBoss JIRA] Created: (JBRULES-2714) Drools Persistence Should Not Rely on an Existing Named Query in "META-INF/orm.xml"

by Anatoly Polinsky (JIRA)

Drools Persistence Should Not Rely on an Existing Named Query in "META-INF/orm.xml" ----------------------------------------------------------------------------------- Key: JBRULES-2714 URL: https://jira.jboss.org/browse/JBRULES-2714 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 5.1.1.FINAL Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor There is a named query "ProcessInstancesWaitingForEvent" that lives in a drools persistence jar under "META-INF/orm.xml". The problem is not even that the query is wrong ( org.hibernate.QueryException: cannot dereference scalar collection element.. ), but that majority of applications that sit on top of JPA rely on its own mappings, and hence this query either: 1. Lost, since the custom "persistence.xml" will redefine the path to other mapping files 2. Will result in "Duplicate query mapping" exception if defined in a custom mapping file ( http://opensource.atlassian.com/projects/hibernate/browse/HHH-4152 ) Would be more logical not to depend that everyone knows to look inside "drools persistence jar", and to have an extensive documentation explaining "ProcessInstancesWaitingForEvent". It maybe hardcoded through @NamedQuery or just be available as an OPTIONAL file to use by Drools clients: e.g. "<mapping-file>META-INF/persistence/mapping/drools/drools-named-queries.xml</mapping-file>" ( and again: documented.. ) /Anatoly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Created: (JBRULES-2798) Allow extraction / injection of constraints in processes

by Kris Verlaenen (JIRA)

Allow extraction / injection of constraints in processes -------------------------------------------------------- Key: JBRULES-2798 URL: https://jira.jboss.org/browse/JBRULES-2798 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assignee: Kris Verlaenen -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
0 / 0

[JBoss JIRA] Created: (JBRULES-2732) ProcessInstancesWaitingForEvent Query is Extremely Inefficient Should Be Simplified

by Anatoly Polinsky (JIRA)

ProcessInstancesWaitingForEvent Query is Extremely Inefficient Should Be Simplified ----------------------------------------------------------------------------------- Key: JBRULES-2732 URL: https://jira.jboss.org/browse/JBRULES-2732 Project: Drools Issue Type: Bug Security Level: Public (Everyone can see) Components: All Affects Versions: 5.1.1.FINAL Environment: N/A Reporter: Anatoly Polinsky Assignee: Mark Proctor "ProcessInstancesWaitingForEvent" query that is used after each process / subprocess ends is extremely inefficient, and since there is no way to force an INDEX without being coupled with JPA provider, this query execution time increase exponentially as the number of processes goes up. Currently with only 20000 processes, the query takes 18(!!!) seconds to execute: <named-query name="ProcessInstancesWaitingForEvent"> <query> SELECT processInstanceInfo.processInstanceId FROM ProcessInstanceInfo processInstanceInfo WHERE :type in elements ( processInstanceInfo.eventTypes ) </query> </named-query> It is inefficient not only because there is no INDEX enforced, but because it goes into the sub query for no good reason. The better/correct query is: SELECT processInstanceInfo.processInstanceId FROM ProcessInstanceInfo processInstanceInfo, EventTypes eventTypes WHERE eventTypes.element = :type AND processInstanceInfo.processInstanceId = eventTypes.processInstanceId In order to get to this "better" query, since it is a JPA one, an EventType/s entity should be created ( it does not currently exist in 5.1.1 ). /Anatoly -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBRULES-2827) Migrate Drools Flow to jBPM5

by Kris Verlaenen (JIRA)

Migrate Drools Flow to jBPM5 ---------------------------- Key: JBRULES-2827 URL: https://issues.jboss.org/browse/JBRULES-2827 Project: Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Kris Verlaenen Assignee: Kris Verlaenen -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
1
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 February 2011