[JBoss JIRA] Created: (JBRULES-1960) Syntaxcoloring wrong if DSL contains a "#"-Character
by Norbert Ziegler (JIRA)
Syntaxcoloring wrong if DSL contains a "#"-Character
----------------------------------------------------
Key: JBRULES-1960
URL: https://jira.jboss.org/jira/browse/JBRULES-1960
Project: JBoss Drools
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: drools-eclipse
Affects Versions: 5.0.0.M5
Environment: eclipse 3.4, WinXP, jre6u10
Reporter: Norbert Ziegler
Assignee: Mark Proctor
Priority: Minor
While editing a DSL-File one can see that everything after an #-Character is colored as comment, regardless of the position of the #.
Indeed, it is not a comment.
Imagine the following line in a DSL:
Compute noselength to #MYVAR * #AGE
then everything at / after "#MYVAR" is rendered as a comment.
In this case a comment should only be recognized if the first non-empty-char of the line is the "#"
--
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
[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
[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
[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