zumbiehl wrote :
| The lookup returns me a null instance of the Spring context although
lookups work fine from within the JBoss container.
|
I think this is expected behavior.
Since we put the bean factory into non-serializable JNDI context, there are no
means of pulling it out from
Hi ,
I have the exact same issue here trying to access the Spring
NamedXmlApplicationContext bound to the global jndi context from a JUnit client.
The lookup returns me a null instance of the Spring context although lookups
work fine from within the JBoss container.
Has anyone been
Hello,
I have the same problem. Have you found a solution yet?
I have JBoss 4.0.4GA and a .ear archive with a bla-server.spring archive
inside. The spring deployer does its job well and the ApplicationContext is
created and registered to local JNDI:
| 11:49:27,755 INFO
the boot sequence of the server :
| Undeploying Spring:
file:/C:/dev/appservers/jbpm-server/server/jbpm/deploy/test3.spring
| Closing application context
[org.jboss.spring.factory.NamedXmlApplicationContext;hashCode=19277415]
| Destroying singletons in factory
i try with JBOss AS 4.0.4 , the result is the same ...
View the original post :
http://www.jboss.com/index.html?module=bbop=viewtopicp=3973197#3973197
Reply to the post :
http://www.jboss.com/index.html?module=bbop=postingmode=replyp=3973197
___
Runtime lookup uses this:
| private Object getObjectFromBeanFactory(Spring spring) throws Exception
| {
| BeanFactory beanFactory = (BeanFactory)
org.jboss.naming.Util.lookup(spring.jndiName(), BeanFactory.class);
| return beanFactory.getBean(spring.bean());
|
thanks but it's still not working, I try this
| public class jndiLookup extends TestCase {
|
| public void testlookup() {
| try {
| Properties jndiProps = new Properties();
|
