#31 Deployment fails on Glassfish 3


Deployment on Glassfish3 fails with following error-message:

Exception while loading the app : java.lang.Exception: java.lang.IllegalStateException: ContainerBase.addChild: start: org.apache.catalina.LifecycleException: org.apache.catalina.LifecycleException: org.springframework.beans.factory.NoSuchBeanDefinitionException: No unique bean of type [com.express.service.ProjectManager] is defined: Unsatisfied dependency of type [interface com.express.service.ProjectManager]: expected at least 1 matching bean


  • adam

    adam - 2010-07-20

    This looks to me like the war that you have is corrupt or didn't load properly in the container. I'm not sure whether Glassfish requires some deployment descriptors not required in simple servlet containers like Tomcat or Jetty, that is another possibility? Another possibility is that the annotations aren't being read, the ProjectManager is specified via annotations.

  • Sven Peetz

    Sven Peetz - 2010-07-21

    Thank you for the hint about deployment descriptors. This should be the way to look for. Annotations should not be a problem.
    I will let you know if I find a workaround one day.
    It probably is not a bug since express is not supposed to run on glassfish.


Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks