[ https://issues.jboss.org/browse/ISPN-5779?page=com.atlassian.jira.plugin.... ]
Pedro Ruivo updated ISPN-5779:
------------------------------
Status: Resolved (was: Pull Request Sent)
Resolution: Done
> TimeService should support java.time.Instant
> --------------------------------------------
>
> Key: ISPN-5779
> URL: https://issues.jboss.org/browse/ISPN-5779
> Project: Infinispan
> Issue Type: Enhancement
> Components: Core
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 8.1.0.Final
>
>
> JDK 8 has introduced java.time which makes it much easier to work with times/dates. TimeService should be enhanced to support it.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-5629?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5629:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 8.1.0.Alpha2
Resolution: Done
> AvgAccumulator should handle NaN and other non-numbers
> ------------------------------------------------------
>
> Key: ISPN-5629
> URL: https://issues.jboss.org/browse/ISPN-5629
> Project: Infinispan
> Issue Type: Bug
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Alpha2, 8.1.0.Final
>
>
> The handling should be similar to java.util.DoubleSummaryStatistics
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-5780?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5780:
----------------------------------
Status: Resolved (was: Pull Request Sent)
Fix Version/s: 8.1.0.Final
Resolution: Done
> SumAccumulator should behave according to JPA spec
> --------------------------------------------------
>
> Key: ISPN-5780
> URL: https://issues.jboss.org/browse/ISPN-5780
> Project: Infinispan
> Issue Type: Bug
> Components: Embedded Querying
> Affects Versions: 8.0.0.Final
> Reporter: Adrian Nistor
> Assignee: Adrian Nistor
> Fix For: 8.1.0.Alpha2, 8.1.0.Final
>
>
> Currently it just preserves the type of the field, which can easily lead to overflow. The JPA spec tries to avoid it by widening the numeric type, see 10.2.7.4. JPQL Aggregate Functions of JPA spec here: http://docs.oracle.com/cd/E12839_01/apirefs.1111/e13946/ejb3_langref.html
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
Tristan Tarrant created ISPN-5792:
-------------------------------------
Summary: Bump server base to WildFly 10.0.0.CR2
Key: ISPN-5792
URL: https://issues.jboss.org/browse/ISPN-5792
Project: Infinispan
Issue Type: Component Upgrade
Components: Server
Reporter: Tristan Tarrant
Assignee: Tristan Tarrant
Fix For: 8.1.0.Alpha2
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
[ https://issues.jboss.org/browse/ISPN-5790?page=com.atlassian.jira.plugin.... ]
Tristan Tarrant updated ISPN-5790:
----------------------------------
Status: Pull Request Sent (was: Pull Request Sent)
Git Pull Request: https://github.com/infinispan/infinispan/pull/3726 (was: https://github.com/infinispan/infinispan/pull/3713)
> AuthorizationManager rework
> ---------------------------
>
> Key: ISPN-5790
> URL: https://issues.jboss.org/browse/ISPN-5790
> Project: Infinispan
> Issue Type: Task
> Reporter: Tristan Tarrant
> Assignee: Tristan Tarrant
> Fix For: 8.1.0.Final
>
>
> The AuthorizationManager has a few issues:
> - it is using the deprecated ClusterRegistry: it should use an internal cache instead
> - it stores per-cache subject ACLs globally, thus possibly returning incorrect ACL masks for a specific subject/cache pair
> Solve the above by introducing a GlobalSecurityManager which starts a global ACL cache and only cache the subject role mapping and not the masks.
> It would be useful if the AuthorizationManager also supported checking for a specific role in addition to a permission
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)