Search:

For anyone else struggling with this problem, here is a solution.

First, this appears to be a bug somewhere inside SpringFramework. After the last object in the slsb pool is closed, you will see...

Even more strange, the final error message says, "please call refresh" but ContextSingletonBeanFactoryLocator is already calling it. This is referenced in the stack trace above too.



protected...

...continued


Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'userdetails-ejb' defined in URL...

HEre is the stack trace after trying invoke the EJB:


Caused by: javax.ejb.CreateException: Could not create stateless EJB
at...

I Have a spring wired stateless ejb that uses the spring bean wiring interceptor. I'm running JDK1.6, spring 3.0.3, and glassfish 3.0.1. I'm using the beanRefContext.xml pattern described in the...

Anyone? :( I don't want to do security in code...

The root of my problem is I would like check an ACL before allowing a method to continue.

SomeService is an external service, therefore I cannot annotate the 'encryptDomainObject' with...

In your beanRefContext.xml, does setting does setting lazy-init=false on the wrapped context do anything? If not, I bet you could extend the interceptor to fix this.

What container?

The SpringBeanAutowiringInterceptor states it will store the ApplicationContext for the EJB in JNDI, that way a new context isn't created every time the EJB is invoked.

My question is: what...

No. If you look at the first box, i'm sending an array of objects... The object in question is called 'TrackedData' which *is*serializable. However, this isn't the problem. The problem is the...

Environment:
websphere 6.1 fp27
spring 2.5.6

This sounds nuts, but it seems to be happening. I have code that takes an object[] and sends a message:

Connection connection = null;
Session...

I think it works beacuse you put the complete lookup string in your spring config. If you put java:comp/env/ejb/TestManager in your web.xml you could probably get rid of the error.

The problem is...

unfortunately no.

It's turns out it's a problem with glassfish 2.1 not honoring the sun-web.xml nor the context.xml. I never found a workaround.

Running Glassfish 2.1, I'm always getting this error:



here is my spring config xml:


here is my web.xml:

and here is my sun-web.xml in my web-inf dir: