Question

I am trying to use spring to provide managed beans to jsf. I assume that @ManagedBean will be picked up by JSF container to link the EL in JSF to managed bean even when I use spring by configuring spring usage in faces-config.xml.

Spring shall provide the beans but now who manages scope of the beans?

I have tried following annotation on beans to have it become Request scope but they do not work.

@ManagedBean(name="helloBean") //meant for JSF
@RequestScoped //meant for JSF
@Scope(value="request") //meant for spring
@Controller //meant for spring
public class HelloBean implements Serializable {

Actually earlier I was using plain JSF and @ManagedBean and @RequestScoped were working well. Now as I tried to integrate using spring the scope are not working.

I have even tried setting bean scope in spring config but they work as expected in context of spring (singleton and prototype) but not web request context.

I was trying to avoid having to use above @Scope and @Controller annotation hoping that JSF will manage scope but do not seem like.

Below are my files snippet for spring config and MyHelloBean which probably will help communicate better.

<bean id="helloBean" class="com.mkyong.common.HelloBean" init-method="init" />

<bean id="myHelloBean" class="com.mkyong.common.MyHelloBean" init-method="init" >
        <property name="helloBean" ref="helloBean"></property>
</bean>

@ManagedBean
@RequestScoped
@Scope(value="request")
@Controller
public class MyHelloBean implements Serializable {

    private static final long serialVersionUID = 1L;
    //@ManagedProperty(value = "#{helloBean}")
    private HelloBean helloBean;

see in above MyHelloBean I am using spring DI to set helloBean which gets set by spring fine. I have commented out @ManagedBean which I think I can leave it in there as it will be ignored by spring any ways and JSF is not going to process it I guess but to be safe I commented it out for JSF to not process it.

To complete I use below in faces-config to activate spring usage.

<el-resolver> 
org.springframework.web.jsf.el.SpringBeanFacesELResolver 
</el-resolver> 

Regards,

Miten.

Answer 1

Your approach is a bit confusing in the sense that it seems that you’re mixing Spring XML configuration and Spring Annotation-based configuration. As described as an example here, if you’re using annotated configuration then you should have:

<context:component-scan base-package="com.yourcom.package" />

to order Spring scan for the annotations. Otherwise, if you’re using XML configuration then you should have:

<bean id="helloBean" class="com.mkyong.common.HelloBean" init-method="init" scope="request" />

as by default the scope for a Spring bean is singleton.