I was excited about the possibility of injecting a session-scoped Spring bean into a dispatcher (since this saves mucking around with ApplicationStateManager) - but (of course!) I've run into a slight problem.
For whatever reason, this syntax: <bean id="myBean" class="foo.MyBean" scope="session"> <aop:scroped-proxy/> </bean> ..creates two visible beans of type MyBean in the Spring app context, the CGLIB proxy (good) and another stray instance (bad). This foils the Tapestry @Inject annotation, which expects only one bean per type (and can't inject by name). Has anyone encountered this and figured out a workaround? One possibility is to wrap the proxied bean with another bean, but this isn't very elegant.
