[
https://issues.apache.org/jira/browse/IOTA-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375375#comment-15375375
]
Barbara Gomes commented on IOTA-25:
-----------------------------------
{quote}
We should also have a boolean parameter for e.g. forcePullJar in the JSON to
enable the user to pull the jar every time a fey JSON is deployed.
{quote}
Swapping a running jar at runtime after Fey has loaded it for some
orchestration is too risky:
1. Previous actors could be using the old instance of the .jar
2. ClassLoader implementation never closes a jar file once it has been opened.
My suggestion for now is to use this configuration for Fey itself.
{code}
fey-global-configuration{
force-pull-jar = false
}
{code}
In this way the jars would be force to update just for the first time it is
being used after Fey was launched.
Later on we can try to use something like OSGi for hot deployment.
> Support HTTP protocol for dynamic population of Fey jar repo
> ------------------------------------------------------------
>
> Key: IOTA-25
> URL: https://issues.apache.org/jira/browse/IOTA-25
> Project: Iota
> Issue Type: New Feature
> Affects Versions: 0.1
> Reporter: Rutvij Clerk
> Assignee: Barbara Gomes
> Priority: Minor
> Fix For: 0.1
>
> Original Estimate: 96h
> Remaining Estimate: 96h
>
> Support HTTP(S) protocol in Fey core to dynamically populate jar repo at
> runtime. As a further refinement, we should also support HTTP Basic Auth for
> protected resources.
> We should also have a boolean parameter for e.g. forcePullJar in the JSON to
> enable the user to pull the jar every time a fey JSON is deployed.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
