[
https://issues.apache.org/jira/browse/SENTRY-219?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14016088#comment-14016088
]
Lenni Kuff commented on SENTRY-219:
-----------------------------------
Fixed this by allowing providerBackend.initialize() to be called multiple
times, subsequent calls are no-ops.
> Sentry Cache Backend Provider initialization does not work as expected
> ----------------------------------------------------------------------
>
> Key: SENTRY-219
> URL: https://issues.apache.org/jira/browse/SENTRY-219
> Project: Sentry
> Issue Type: Bug
> Affects Versions: 1.4.0
> Reporter: Lenni Kuff
> Assignee: Lenni Kuff
> Attachments: SENTRY-219.patch
>
>
> Currently, the usage is meant to be:
> # Create a ProviderBackend
> # Create a ProviderBackendContext and call setHandle()
> # Call providerBackend.initialize(providerContext);
> # Create a SimpleDbPolicyEngine and pass the "initialized()" provider backend.
> However, creating a SimpleDbPolicyEngine will creates a new
> ProviderBackendContext in the ctor and calls ProviderBackend.initialize()
> effectively wiping out the handle that was set previously. The workaround is
> to call initialize() on the ProviderBackend again, after creating the policy
> engine.
> Perhaps, initialize() can be a no-op if it has already been called?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
