[JBoss JIRA] (ISPN-7363) Allow @Input caches to Runnables in CDI
by Sebastian Łaskawiec (JIRA)
[ https://issues.jboss.org/browse/ISPN-7363?page=com.atlassian.jira.plugin.... ]
Sebastian Łaskawiec updated ISPN-7363:
--------------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 9.0.0.CR2
9.0.0.Final
Resolution: Done
> Allow @Input caches to Runnables in CDI
> ---------------------------------------
>
> Key: ISPN-7363
> URL: https://issues.jboss.org/browse/ISPN-7363
> Project: Infinispan
> Issue Type: Bug
> Components: CDI Integration
> Affects Versions: 9.0.0.Beta1
> Reporter: Sebastian Łaskawiec
> Assignee: Sebastian Łaskawiec
> Fix For: 9.0.0.CR2, 9.0.0.Final
>
>
> Currently injecting {{@Input}} caches work only for {{Callable}}. Since {{DefaultExecutorService}} supports also {{Runnable}}, we should also support injecting {{@Input}} caches there.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPN-7464) Make caffeine optional dependency for infinispan core
by William Burns (JIRA)
William Burns created ISPN-7464:
-----------------------------------
Summary: Make caffeine optional dependency for infinispan core
Key: ISPN-7464
URL: https://issues.jboss.org/browse/ISPN-7464
Project: Infinispan
Issue Type: Bug
Components: Eviction
Reporter: William Burns
Fix For: 9.0.0.CR2
Caffeine should be optional dependency for commons and internal dependency for core and hotrod-client. This needs to be applied to maven and wildfly.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month
[JBoss JIRA] (ISPRK-2) Management of cache lifecycles
by Gustavo Fernandes (JIRA)
[ https://issues.jboss.org/browse/ISPRK-2?page=com.atlassian.jira.plugin.sy... ]
Gustavo Fernandes updated ISPRK-2:
----------------------------------
Status: Open (was: New)
> Management of cache lifecycles
> ------------------------------
>
> Key: ISPRK-2
> URL: https://issues.jboss.org/browse/ISPRK-2
> Project: Infinispan Spark
> Issue Type: Feature Request
> Reporter: RJ Nowling
> Fix For: 0.5
>
>
> For analytics use cases, the caches will rarely be known ahead of time -- they are dependent on the particular jobs being run. As such, jobs should have the ability to manage the lifecycle of caches, in particular:
> * Checking if a cache exists
> * Creating a cache
> * Deleting a cache
> * Clearing a cache
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 1 month