Using context lookup strategies in flow definitions

[Tom Zeller]

A quick note : maybe we should try to use context lookup strategies
when assigning Web Flow variables. For example, I believe the
following

<evaluate expression="opensamlProfileRequestContext"
 result="viewScope.profileRequestContext" />

<evaluate expression="SetRPUIInformation.getRPUIContextCreateStrategy().apply(opensamlProfileRequestContext)"
 result="viewScope.rpUIContext" />

is equivalent to

<evaluate expression="opensamlProfileRequestContext"
 result="viewScope.profileRequestContext" />

<evaluate expression="opensamlProfileRequestContext.getSubcontext(T(net.shibboleth.idp.authn.context.AuthenticationContext))"
 result="viewScope.authenticationContext" />

<evaluate expression="authenticationContext.getSubcontext(T(net.shibboleth.idp.ui.context.RelyingPartyUIContext))"
 result="viewScope.rpUIContext" />

but does not "hard-code" context hierarchy navigation in the flow definition.