Possibly, but I've got hundreds of code-generated database converters registered by type. I'd hate to have to go in and manually specify a converter every place a database entity type is used.
In both case, it's a workaround for what I consider a current weakness in JSF. Converters and validators should be able to have bindings to other managed beans via the config file. On 8/31/05, Craig McClanahan <[EMAIL PROTECTED]> wrote: > On 8/31/05, Ken Weiner <[EMAIL PROTECTED]> wrote: > > The Spring JSF integration I've seen focuses on enabling Spring IoC for > JSF managed beans. There is a way to enable IoC for JSF Converters, > Validators, and UIComponents too. I posted information on the Spring JSF > Wiki: > http://opensource.atlassian.com/confluence/spring/x/Qgo > > I was hoping Spring would incorporate the SpringApplication and > SpringApplicationFactory code in a future release, but there haven't yet > been comments on the Wiki page. > > > For converters, isn't this already possible out of the box (if you've got > the Spring IoC integration with managed beans)? > > <h:inputText ... converter="#{myConverter}" .../> > > where "myConverter" is a spring bean. > > For validators, you can bind to a validator *method* of some bean that > happens to be created via the IoC facility. > > -Ken > > Craig > >
