Yes I agree with you but it would be great to be able to use the clean EL syntax of JSF managed beans in the xml files. To refer aother bean property in spring, you need to declare it using a special bean wich is very verbose.
The mixing approach you talking about is because we confuse two concepts here. Declarative programming and configuration. For instance, declaring a bean stateful has nothing to do with the configuration because if you change it to stateless your code need some changes. A datasource url is a configuration and need to be put in a centralized configuration. This changes has no impact on your code. I think the confusion comes from the fact that a configuration is declarative by nature. On 1/13/06, Werner Punz <[EMAIL PROTECTED]> wrote: > Alexandre Poitras schrieb: > > The thing I like about JSF managed beans is the clean EL syntax > > instead of the very verbose xml language (I have nothing against xml > > files but I do think we abuse its usage). I hope Spring IoC container > > adopt it one day if it is possible. But using annotations is going to > > be even better :) Can't wait! > > > > I personally love the EJB3 @Bean @inject @outject paradigm > very clean and tight. > > I think things like bean definitions at least should have the optional > option of annotations, I do not thing blocking the xml way is good at > all, in many situations you need a centralized configuration of things. > But in many you do not need it, a mixed approach in this area might be > the best way to go. > > -- Alexandre Poitras Québec, Canada
