Changes to web flow action proposal

[Brent Putman]

On 4/20/13 1:15 PM, Cantor, Scott wrote:
>> <beans default-autowire="byType"
>> default-autowire-candidates="shibboleth\.ProfileRequestContext" ... />
> That limits what it considers for injection, but not what it looks at to
> inject into. So once you turn an autowiring setting on globally, it looks
> at every property of a given name or type on every bean for possibly
> injection. The limiting then reduces the pool of candidate beans to
> prevent ambiguity.

Yes, exactly.  Which depending on what we're doing, might in theory be ok.  E.g. if something has a
ProfileRequestContext slot on it, chances are we probably want that injected.  I suspect they do
this by modifying the BeanDefinition (probably with a BeanFactoryPostProcessor), so it's just a
one-time upfront cost.

>
>>  Autowiring isn't necessarily the best way
>> to solve the concerns we
>> were discussing today with respect to wiring the contexts and/or
>> requests/responses: 

>> Yes, I'm fairly certain it's not the best way.

Yeah, there's probably better ways.