That is fine, but I'm specifically looking to have the EJBs able to lookup without first defining it in Spring, and further to be able to inject spring beans with @Resource. Being the lead developer I develop the inhouse frameworks/layouts/idioms, so other developers can follow an easy straightforward path.
To have to initialize all EJBs first I might as well just @EJB them. Though what you suggested is the good way to do it, and in the mean time (until I find the complete solution) I'll do it that way. Thanks, this way I should still be able to AOP the hell out of my project. Q On Fri, Sep 11, 2009 at 1:37 PM, Fredrik Jonson <[email protected]> wrote: > Quintin Beukes wrote: > >> I had a look at the Spring in OEJB 3.1. Works well. Very nice feature. >> My question is how I can get the same running in Geronimo. > > I've used spring for webapps in G. Spring can be configured to lookup javaee > managed resources from jndi environment, and inject those as beans in the > context: > > <jee:jndi-lookup id="myEjb" jndi-name="MyEjbBean" resource-ref="true" /> > <bean id="somePojo" class="org.example.some.SomePojo""> > <property name="myEjb" value="myEjb"/> > </bean> > > http://static.springsource.org/spring/docs/2.5.x/reference/xsd-config.html > > -- > Fredrik Jonson > > -- Quintin Beukes
