Is the following still the best way to inject Spring beans into a page when testing?
http://wiki.apache.org/tapestry/Tapestry5SpringIntegrationAlternative1 With Tapestry 4, I could populate a Map with with the bean name and a real (or mock) implementation and instantiate the page, then call methods accordingly. Is this possible with Tapestry 5 w/o creating a lot of infrastructure code (which the above seems to require)? Thanks, Matt -- View this message in context: http://www.nabble.com/-T5--Testing-Pages-with-injected-Spring-beans-tp21057429p21057429.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
