If I define a bean in faces-spring-config as singleton="false", scope managed and set to session by JSF by defining the same bean as SpringBeanScope class in faces-config, the bean is always re-created as if its scope was request. It works as expected (bean scope is session) if I define the same bean in applicationContext.xml instead. Is this a bug or feature and if a feature, is it possible to change this behaviour in a future release? Running Spring 3.0.0M1, Spring 1.2 and MyFaces 1.09 2005-07-25.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If I define a bean in faces-spring-config as singleton="false", scope managed and set to session by JSF by defining the same bean as SpringBeanScope class in faces-config, the bean is always re-created as if its scope was request. It works as expected (bean scope is session) if I define the same bean in applicationContext.xml instead. Is this a bug or feature and if a feature, is it possible to change this behaviour in a future release? Running Spring 3.0.0M1, Spring 1.2 and MyFaces 1.09 2005-07-25.
It's a bug. We will check it an try to fix the problem with the next release.
Perfect. Thanks a lot for quick answer.