|
From: Bill B. <bb...@re...> - 2008-10-09 04:48:33
|
Solomon Duskis wrote: > Re ResourceExposingService - I guess it was a bad name... I basically > meant ResteasyRegistration. I do hope this makes it into the RESTEasy core. > > Re IoC container dependency: What I really want is a way to use the > Spring MVC framework right along side JAX-RS/RESTEasy. It will allow me > to configure which requests go to Spring MVC Controllers/Struts > Actions/JAX-RS Resources and how to render Views/Producers with > Velocity/Freemarker/Tiles/JSP. In order to get that to work properly, > I'll need to store the Registry et al in the Spring Application context > instead of the ServletContext. > Why do you need access to the Registry? And if you really do, can't it be manually registered? > Perhaps I'll just vet some ideas in this group as to how I could use > RESTEasy towards my ends. The means I use to achieve my ends may may be > helpful for other MVC and IoC integrations such as Struts2/Guice... I > know RESTEasy already works with Seam ;). > Yes, please brainstorm. I'm Spring ignorant beyond basic IoC so any insight would be invaluable. -- Bill Burke JBoss, a division of Red Hat http://bill.burkecentral.com |