StorageBackedSessionManager Contract

[Marvin Addison]

On Tue, Sep 20, 2016 at 8:43 AM Cantor, Scott <cantor.2 at osu.edu> wrote:

> Using the client storage service absolutely requires that the data get
> loaded explicitly first. It can't distinguish between the data not being
> loaded and an empty store if it just auto-initialized the store, so it has
> a constraint baked in to make sure that the system outright breaks if the
> flow isn't using the service correctly.
>

I'm trying to handle what I would think is a common case, where the data
for the key doesn't exist. Throwing a RuntimeException in that case is
perfectly acceptable, but it would be nice to have it documented somewhere.
(If it is documented, then I missed it.) The only wrinkle in my case is
that I don't want to abort the flow, which appears to be how the session
management components handle it via the standard flow error handling
routine. So I do need to explicitly trap the exception in my case, either
in the component or in the controlling flow.

M <dev-unsubscribe at shibboleth.net>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160920/0f629153/attachment-0001.html>