Actions not identified/identifiable?

[Brent Putman]

On 9/25/16 4:41 PM, Cantor, Scott wrote:
> On 9/25/16, 4:26 PM, "dev on behalf of Tom Zeller" <dev-bounces at shibboleth.net on behalf of tzeller at dragonacea.biz> wrote:
>
>>    Just added another test to verify that the
>>    IdentifiableBeanPostProcessor does indeed run on singleton beans in a
>>    simple Spring application context, not sure what SWF is doing.
> It's deeper. From what I can tell, SWF doesn't run them at all, singletons or prototypes, I just had to get past the singletons to find the rest breaking.
>
> Spring is supposed to auto-install and run those post processors and it does except inside SWF. But the weird thing is the action post-processor does run, obviously. One difference is one of them hooks pre-init and the other post-init. Maybe that's involved, don't know yet.
>
> This is worth bottoming out either way since we have this stuff all declared and it turns out to not work.


I haven't looked into this really, but it occurs to me that:  IIRC,
every SWF flow creates its own Spring ApplictionContext (I think as a
child of the MVC DispatcherServlet one).  I didn't personally even know
this until I wrote some code once to output some debug logging of the
Spring context tree.

Anyway, could that be related?  I don't think bean post-processors are
inherited by child contexts, are they?  I'm not 100% sure.  But if
they're not, and if you aren't doing something to explicitly wire the
post-processor(s) into the bean set of every concrete flow, then that
could be the reason. 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/dev/attachments/20160926/6dcccce8/attachment.html>