[JBoss JIRA] (DROOLS-3090) KieScanner does not work as expected
by Mario Fusco (Jira)
[ https://issues.jboss.org/browse/DROOLS-3090?page=com.atlassian.jira.plugi... ]
Mario Fusco commented on DROOLS-3090:
-------------------------------------
I'm sorry but I don't see how I could investigate this problem without a reproducer. Do you think that you could attach a small one? Thanks.
> KieScanner does not work as expected
> ------------------------------------
>
> Key: DROOLS-3090
> URL: https://issues.jboss.org/browse/DROOLS-3090
> Project: Drools
> Issue Type: Bug
> Components: core engine
> Affects Versions: 7.8.0.Final
> Reporter: Ales Dolecek
> Assignee: Mario Fusco
> Priority: Major
> Attachments: kmodule.xml, spring.xml
>
>
> We have published nee version of rules:
> {noformat}
> 2018-10-09 10:44:58,785 INFO [Timer-2][] ScannerListener Knowledge base scanner SCANNING
> 2018-10-09 10:44:59,019 INFO [Timer-2][] ScannerListener Knowledge base scanner UPDATING
> 2018-10-09 10:45:00,236 INFO [Timer-2][] KieRepositoryImpl KieModule was added: ZipKieModule[releaseId=cz.dimensiondata.o2:offline-rules:0.0.20,file=F:\GCTI8\assign_manager_2\repository\cz\dimensiondata\o2\offline-rules\0.0.20\offline-rules-0.0.20.jar]
> 2018-10-09 10:45:00,345 INFO [Timer-2][] KieScanner The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20}
> 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING
> 2018-10-09 10:45:00,345 INFO [Timer-2][] ScannerListener Knowledge base scanner RUNNING
> {noformat}
> As you can see the jar got downloaded to local M2 repository and replace. Yet drools still uses old rules.
> We have 3 artefacts:
> offline-facts - with classes inserted into operation memory
> offline-rules - with rules in 1 DRL file and 2 XLSX file
> offline-server - with the application code
> offline-server depend on offline-facs (so it can create new insances)
> offline-rules depend on offline-facts as well, but with provided scope (so the one on classpath is used)
> I have found that Maven has its own caching mechanism so even if new version is published it wont check remote repository more ften than once a day. This can be solved by setting update policy to always.
> {code}
> <repositories>
> <repository>
> <id>public</id>
> <name>Public Repositories</name>
> <url>https://example.org/nexus/content/groups/public/</url>
> <releases>
> <updatePolicy>always</updatePolicy>
> </releases>
> <snapshots>
> <updatePolicy>always</updatePolicy>
> </snapshots>
> </repository>
> </repositories>
> {code}
> Everything seems configred correctly. Fragments of spring configuration are added.
> I'm bit confused what the message:
> {code}
> The following artifacts have been updated: {cz.dimensiondata.o2:offline-rules:0.0.19=cz.dimensiondata.o2:offline-rules:jar:0.0.20}
> {code}
> actually means.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3073) Wrong full package if you use classes from another folder
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3073?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3073:
-------------------------------------
Story Points: 1
> Wrong full package if you use classes from another folder
> ----------------------------------------------------------
>
> Key: DROOLS-3073
> URL: https://issues.jboss.org/browse/DROOLS-3073
> Project: Drools
> Issue Type: Bug
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Major
> Attachments: Screenshot from 2018-10-05 15-32-12.png, scesim.zip
>
>
> Step to reproduce:
> - Create a Data Object "Object1" in a specific package (i.e. com.myspace.myproject)
> - Create a Test Scenario (Preview) "Test1" in a different package (i.e. com.myspace)
> - Use Data Objects tab to import "Object1" to "Test1"
> - Reload the asset and map a field of "Object1" to a column
> - Fill "Test1" with valid values
> - Run the scenario
> Result: Impossible to load class com.myspace.Object1
> Minor bug: if "Test1" has been create in default package the error that you get is "Impossible to load class *.*Object1" so it should be impossible to create the asset into default package or it should consider it to avoid "." symbol at the beginning
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3053) Warning popup of column type change in Scenario grid
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3053?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3053:
-------------------------------------
Story Points: 5
> Warning popup of column type change in Scenario grid
> ----------------------------------------------------
>
> Key: DROOLS-3053
> URL: https://issues.jboss.org/browse/DROOLS-3053
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
> Labels: UX, UXTeam
> Attachments: Screenshot from 2018-10-04 17-44-51.png, Screenshot from 2018-10-04 17-45-21.png, warning2.png
>
>
> Implement a warning popup when the user changes the type of a column that has been already populated.
> To be done/merged *after* DROOLS-3051.
> *Acceptance criteria*
> - If the column contains no value, no confirmation is needed
> - If old and new types are the same the user has to decide if the values should be removed or not
> - If old and new types are not the same the user has to accept that old values will be removed
> - All warning popups should contains also a "Cancel" command to abort the edit
> - If the user try to update the column type with the same column type no warning should be raised and data should stay untouched
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months
[JBoss JIRA] (DROOLS-3052) Implement read only mechanism for the cells in Scenario grid
by Gabriele Cardosi (Jira)
[ https://issues.jboss.org/browse/DROOLS-3052?page=com.atlassian.jira.plugi... ]
Gabriele Cardosi updated DROOLS-3052:
-------------------------------------
Story Points: 3
> Implement read only mechanism for the cells in Scenario grid
> ------------------------------------------------------------
>
> Key: DROOLS-3052
> URL: https://issues.jboss.org/browse/DROOLS-3052
> Project: Drools
> Issue Type: Task
> Components: Scenario Simulation and Testing
> Reporter: Daniele Zonca
> Assignee: Gabriele Cardosi
> Priority: Minor
>
> Update ScenarioGridColumn and ScenarioGridCell to support read only mode.
> ScenarioHeaderMetaData already has a similar mechanism so it is probably possible to define a common interface to abstract this behaviour
> *Acceptance criteria*
> - If a column is in read only mode all the contained cells have to be read only
> - If a cell/column is in read only mode, inline editing should be disabled
--
This message was sent by Atlassian Jira
(v7.12.1#712002)
7 years, 7 months