more work on idp-distribution

[Cantor, Scott]

On 8/23/13 6:29 PM, "Tom Zeller" <tzeller at dragonacea.biz> wrote:

>I thought this, the model, was the reason for contexts, I mean
>OpenSAML messaging BaseContexts.
>
>Grab the ProfileRequestContext from the Spring Context and we are all
>good, I thought.

Yes, the trick is, how do you get the Spring Context? The VelocityContext
the ViewResolver builds only has a "model" parameter that is, I think, the
model injected via the view-state element. I don't know how or if the
template can acess the Spring RequestContext.

If nothing else, it's poorly documented how all this view stuff works in
the Spring-MVC docs. It really assumes you know MVC pretty well, I guess,
which is not the case for me.

I know that in the JSP case, if nothing else, there are always Java tricks
one can use to tunnel in objects, but with Velocity, all you have is the
macro context, and it's not exposed via Spring-MVC that I can see. If
there are "implicit" objects they inject, they don't seem to be documented
that I can find.

What they seem to assume is that you're doing the standard MVC thing and
your data is in a model you layer into the view, and then bind the results
back into. Which is way more work than I had hoped I'd have to do to
accomplish what I do now with a trivial rendering class. ;-)

-- Scott