8000 Alfresco uses AclEntity as cache key · Issue #62 · aldica/aldica · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
Alfresco uses AclEntity as cache key #62
Open
@AFaust

Description

@AFaust

This issue does not denote a bug in our module, but serves to document a design issue found in default Alfresco. Specifically, as part of work on #38, it was found that Alfresco uses instances of the complex AclEntity class as cache keys in both the AclDAOImpl and PermissionServiceImpl. This type of use is highly irregular, and is made even worse by the fact that the use case relies on a deliberately partial implementation of hashCode and equals within the AclEntity class.

Since this kind of irregular use causes issues with Ignite-backed caches, which use the entire serialiesd state for hashCode / equals on serialised objects to avoid the overhead of temporarily deserialising them and using the actual implementation, a workaround had to be implemented in commit 3c5a6b7
Nevertheless, this should be fed back to Alfresco either as a simple issue or a PR with an appropriate correction.

Metadata

Metadata

Assignees

Labels

alfresco designThis is affected/caused by technical design of Alfrescoupstream issueIssue with an upstream dependency, e.g. Alfresco, Ignite or other

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0