Aug 12th, 2008, 09:00 AM
Spring webapp, EJB backend redeployed: NoSuchEJBException?
maybe an obvious thing I ran into: Having a Spring/MVC based webapp built against a couple of backend services being stateless EJBs, things work pretty good - except for having the backend application redeployed without redeploying the webapplication as well, which then is likely to cause any EJB calls end up in NoSuchEJBException's being thrown. Somehow I am not surprised to see this happen (given the EJB references obviously are injected along with the Spring application context startup), still the question: Is there a way to, in such a setup, avoid having to redeploy the webapp as well?
TIA and best regards,
Jul 19th, 2009, 10:33 PM
I realise this is a very old thread, but did anyone find the solution to this problem? Rebuilding the flow somehow seems to help? Eg, if I start a new flow, it picks up the new EJB, while reusing the current flow doesn't.
Edit: In my case, we were looking up the EJB in an Action constructor instead of in the setupForm method, so when the new form got setup it was using a stale EJB reference. It's important to keep in mind when the objects you're working with are being instantiated...
Last edited by richard.barrington; Jul 20th, 2009 at 12:09 AM.
Jul 20th, 2009, 01:50 AM