Shibboleth Developers

[Christopher Bongaarts <>]

Brent Putman wrote:
> Another way would be to use Spring.  Just define the value as a Spring
> bean (even a plain String can be a bean) in say internal.xml, and then
> it's accessible from anywhere you can get at the Spring app context.
> The "easy" way would be to just assume a fixed bean id and then just
> hardcode that bean id in your LoginHandler's bean definition parser and
> servlet init code.  Servlet can get access to the Spring app context
> using standard Spring conventions.

Can I get a quick one-liner/hint about how to do that?

I think I get how to define the bean in internal.xml and how to write 
the bean class; what I'm looking for is how to get at it from the login 
handler and servlet (or, from what I understand of how Spring works, how 
to set things up so the values magically get injected into the right spots).

By "even a plain String can be a bean" does that mean I can avoid 
writing a specific bean class and its associated parser?

--
%%  Christopher A. Bongaarts   %%  

          %%
%%  OIT - Identity Management  %%  http://umn.edu/~cab  %%
%%  University of Minnesota    %%  +1 (612) 625-1809    %%