[JBoss JIRA] (DROOLS-3810) Enable a fast forward system to skip already processed events
by Massimiliano Dessi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3810?page=com.atlassian.jira.plugi... ]
Massimiliano Dessi updated DROOLS-3810:
---------------------------------------
Description: Provide a method with the key to use as a trigger to restart
> Enable a fast forward system to skip already processed events
> -------------------------------------------------------------
>
> Key: DROOLS-3810
> URL: https://issues.jboss.org/browse/DROOLS-3810
> Project: Drools
> Issue Type: Sub-task
> Environment: Using the identifier data of the last processed event on the Control topic , we need to skip the event on the topic from the head without procesing and start the work on the events only when the last rpocessed event is found on the events topic
> Reporter: Massimiliano Dessi
> Assignee: Massimiliano Dessi
> Priority: Major
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> Provide a method with the key to use as a trigger to restart
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-3825) Model compiler should not duplicate files across runs
by Edoardo Vacchi (Jira)
Edoardo Vacchi created DROOLS-3825:
--------------------------------------
Summary: Model compiler should not duplicate files across runs
Key: DROOLS-3825
URL: https://issues.jboss.org/browse/DROOLS-3825
Project: Drools
Issue Type: Bug
Reporter: Edoardo Vacchi
Assignee: Edoardo Vacchi
If you don't {{mvn clean}} each time you generate the executable model, new files will be generated at each run.
These seem to be the culprit:
{{PackageModel#getPackageUUID}}
{code}
private String generateRulesFileName() {
return RULES_FILE_NAME + generateUUID();
}
{code}
solution: use a counter; the compiler is single-threaded, two runs produce the same output, existing files will be just overwritten
deliverable: test case verifying files do not grow in number across runs
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months
[JBoss JIRA] (DROOLS-3798) [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see those nodes in the graph on read-only mode
by Guilherme Gomes (Jira)
[ https://issues.jboss.org/browse/DROOLS-3798?page=com.atlassian.jira.plugi... ]
Guilherme Gomes updated DROOLS-3798:
------------------------------------
Summary: [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see those nodes in the graph on read-only mode (was: [DMN Designer] Included Models - Show imported nodes in the graph when a DMN with imported nodes is opened)
> [DMN Designer] Included Models - When users open a DMN file with imported nodes, they must be able to see those nodes in the graph on read-only mode
> ----------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: DROOLS-3798
> URL: https://issues.jboss.org/browse/DROOLS-3798
> Project: Drools
> Issue Type: Task
> Components: DMN Editor
> Reporter: Guilherme Gomes
> Assignee: Daniel José dos Santos
> Priority: Major
> Labels: drools-tools
> Attachments: daniel1.dmn, daniel2.dmn
>
>
> When users open the DMN editor with an imported file+ imported nodes, they must be able to see these nodes on read-only mode.
> ---
> Assets:
> - [^daniel1.dmn]
> - [^daniel2.dmn]
> ---
> This task comprehends:
> - Read imported nodes in the "daniel2.dmn", and put them into the canvas by consuming a *mocked service class* [1] to fill the node information;
> - Create the new imported nodes in the canvas;
> - Persist imported nodes info properly in the DMN file (when users save it);
> - Keep these imported nodes on read-only mode;
> - Keep the properties panel correctly updated.
> ---
> Acceptance criteria:
> - Open the "daniel2.dmn"
> - See the imported nodes from the "daniel1.dmn"
> - Try to change the name of the node (this should not be allowed, since the node must be on read only mode)
> - Check the properties panel properties
> ---
> [1] This service class will be responsible for returning all information from a given node from another DMN file. This API will be something like this: {{ExternalDMNFileService.getNode(final String dmnElementRef)}}
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
6 years, 6 months