> (Maybe should be moved to the user list...) > My recipe (for better or worse) is to use Spring with JSF-Spring, which > offers the same functionality. The latest JSF-Spring, 3.0.0M3, has fixed
Yes, right. JSF-Spring has nice features, using faces scopes for spring managed beans, using spring-aop inside of faces-cfg by defining "DefaultAdvisorAutoProxyCreator" as an application scoped managed bean. and so on. have in mind, that JSF-Spring is *not* part of the springframework. http://jsf-spring.sf.net Spring itself also contains jsf support, but that is *only* a VariableResolver to be able to define your backing beans in applicationContext.xml, or even wire your backing bean properties w/ some spring managed daos -Matthias > all my little issues with it. The Spring bean creation is just much more > flexible than JSF's and dependency injection offers a nice way to > separate my UI backing beans from business beans. The one architectural > issue is how to generically deal with null beans and exceptions that > using factories inevitably cause. At the moment I'm using a > TilesController to do forwarding in cases where necessary parameters for > factory operations were not passed in and the factory would throw an > exception and/or null objects. Not absolutely convinced that's the best > way though, and this of course only works with Tiles, but the latter is > fine in my case. > > Kalle > -- Matthias Wessendorf Zülpicher Wall 12, 239 50674 Köln http://www.wessendorf.net mwessendorf-at-gmail-dot-com
