DelegatingVariableResolver not resolving Spring beans

Question

I'm developing an application using ADF UI + Spring using Jdveloper11g and deploying it to Weblogic 10.3. I'm creating beans in Spring and injecting them into ADF as managed beans(via faces-config.xml). My faces-config.xml looks like:
-------------snip-----------------------
<?xml version="1.0" encoding="windows-1252"?>
<faces-config version="1.2" xmlns="http://java.sun.com/xml/ns/javaee">
<application>
<default-render-kit-id>oracle.adf.rich</default-render-kit-id>
<variable-resolver>org.springframework.web.jsf.DelegatingVariableResolver</variable-resolver>
</application>
<managed-bean>
<managed-bean-name>engineAspect</managed-bean-name>
<managed-bean-class>com.x.EngineAspect</managed-bean-class>
<managed-bean-scope>request</managed-bean-scope>
<managed-property>
<property-name>engineAspect</property-name>
<value>#{engineAspect}</value>
</managed-property>
</managed-bean>
</faces-config>
-------------snip-----------------------
I'm using a backing bean to call a method on the engineAspect bean when some action happens in the UI. But, the line System.out.println(engineAspect); in the backing bean always prints a null. The backing bean has getter and setter for this field. Yet, the bean is not resolved from Spring. Any ideas what may be missing from the configuration?

Answer 1

Miku wrote:
I have a situation where I need to use spring beans from an EJB 3.0 MDB. The project does not have any webapps or anything,
it will be only a MessageBean facade that needs to call spring beans. It is meant to be a service, that can be called by usign a single EJB message. Why not make it a real service? Spring's contract first web services are a very nice way to go. It hides the fact that you're using a message-driven component for processing, too.
%