If it's relevant I have the xfire service I'm targeting exposed on a path that is ignored by Tapestry (using IgnoredPathsFilter), so perhaps this is why Tapestry is not injecting the service into the Spring bean - the tapestry service I'm trying to inject is visible as DEFINED in the iocregistry. How to have Tapestry pay attention to injection while not treating the url the xfire service is exposed at as an invalid page and defaulting to the app start page ...? Really blocked on this - would love any steers ...
Regards, Jim. -----Original Message----- From: Jim O'Callaghan [mailto:j...@peritussolutions.com] Sent: 05 January 2010 13:02 To: Tapestry users Subject: Accessing Tapestry Services from Spring Beans Is it possible to access Tapestry Services from Spring Beans? Having looked through the forum I've found posts mentioning injecting Tapestry Services inside Spring Beans using the annotations: @Inject @Autowired ... but am finding my referenced services are null rather than proxies for JIT creation. I'm using Tapestry 5.1.0.5 and don't have tapestry.use-external-spring-context set to true. Is there some other config required? I'm probably missing something obvious. Background is I'm trying to use XFire and Spring for some web services that are a bit verbose for the RESTful approach (though the t5 restful services works nicely out of the box), and I would rather not duplicate my hibernate / envers / custom interceptors config for Spring when it's there already for Tapestry. Would be grateful for any hints / pointers to resources / example, esp. ones where the injection / autowire / etc. is not in the pages / components area - this is a standalone service I'm trying to access the Tapestry service from. Regards, Jim. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
