[jboss-jira] [JBoss JIRA] (DROOLS-1008) KieServer to update container for SNAPSHOT kjar
Andrew Collins (JIRA)
issues at jboss.org
Wed Jan 27 09:50:00 EST 2016
[ https://issues.jboss.org/browse/DROOLS-1008?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Collins updated DROOLS-1008:
-----------------------------------
Description:
Description of problem:
When a kjar is a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup. Retrieving a new snapshot version is only possible through use of KieScanner.scanNow(), which will both fetch the new artifact from the remote repository, and reload the kmodule in the KieServer JVM.
was:When a kjar is a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup. Updating a KieContainer to a newer snapshot version is only possible through use of the KieScanner, which will both fetch the new artifact from the remote repository, and reload the kmodule in the KieServer JVM.
> KieServer to update container for SNAPSHOT kjar
> -----------------------------------------------
>
> Key: DROOLS-1008
> URL: https://issues.jboss.org/browse/DROOLS-1008
> Project: Drools
> Issue Type: Feature Request
> Components: kie server
> Affects Versions: 6.2.0.Final, 6.3.0.Final
> Reporter: Andrew Collins
> Assignee: Mario Fusco
> Attachments: snapshot_kjar_reproducer.patch
>
>
> Description of problem:
> When a kjar is a snapshot version, kie-server will not react to new snapshot versions deployed to a remote artifact repository. The remote artifact repository is only queried the first time after JVM startup. Retrieving a new snapshot version is only possible through use of KieScanner.scanNow(), which will both fetch the new artifact from the remote repository, and reload the kmodule in the KieServer JVM.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list