[jboss-user] [JBoss Seam] - Problem upgrading to Seam 2.0.1.CR1
seamdev
do-not-reply at jboss.com
Wed Dec 19 12:46:54 EST 2007
After upgrading libraries from Seam 2.0.0.GA to Seam 2.0.1CR1, I get following error at deploy time (deploying to weblogic 9.2.2):
| Target state: deploy failed on Server AdminServer
| java.lang.NullPointerException
| at org.jboss.seam.contexts.ServletLifecycle.endInitialization(ServletLifecycle.java:97)
| at org.jboss.seam.init.Initialization.init(Initialization.java:573)
| at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:34)
| at weblogic.servlet.internal.EventsManager$FireContextListenerAction.run(EventsManager.java:376)
| at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:321)
| at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:121)
| at weblogic.servlet.internal.EventsManager.notifyContextCreatedEvent(EventsManager.java:82)
| at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java:1608)
| at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2750)
| at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:889)
| at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:333)
| at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
| at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
| at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
| at weblogic.application.internal.flow.ScopedModuleDriver.start(ScopedModuleDriver.java:200)
| at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java:117)
| at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:204)
| at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
| at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:60)
| at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:26)
| at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:635)
| at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:26)
| at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:212)
| at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java:154)
| at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.java:80)
| at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOperation.java:566)
| at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(ActivateOperation.java:136)
| at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOperation.java:104)
| at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperation.java:320)
| at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(DeploymentManager.java:815)
| at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(DeploymentManager.java:1222)
| at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.java:433)
| at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServiceDispatcher.java:161)
| at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommitCallback(DeploymentReceiverCallbackDeliverer.java:181)
| at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$100(DeploymentReceiverCallbackDeliverer.java:12)
| at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(DeploymentReceiverCallbackDeliverer.java:67)
| at weblogic.work.ServerWorkManagerImpl$WorkAdapterImpl.run(ServerWorkManagerImpl.java:518)
| at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
| at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
|
I have included following seam jars in my app:
| activation.jar antlr.jar
| cglib.jar commons-beanutils.jar
| commons-collections.jar commons-digester.jar
| commons-logging.jar dom4j.jar
| el-api.jar el-ri.jar
| hibernate-annotations.jar hibernate-commons-annotations.jar
| hibernate-entitymanager.jar hibernate-search.jar
| hibernate-validator.jar hibernate.jar
| javassist.jar jboss-archive-browsing.jar
| jboss-common-core.jar jboss-container.jar
| jboss-dependency.jar jboss-el.jar
| jboss-embedded-api.jar jboss-jmx.jar
| jboss-kernel.jar jboss-logging-spi.jar
| jboss-seam-debug.jar jboss-seam-gen.jar
| jboss-seam-ioc.jar jboss-seam-mail.jar
| jboss-seam-pdf.jar jboss-seam-remoting.jar
| jboss-seam-ui.jar jboss-seam.jar
| jboss-system.jar jsf-api.jar
| jsf-facelets.jar jsf-impl.jar
| jsr181-api.jar jsr250-api.jar
| jstl.jar persistence-api.jar
| richfaces-api.jar richfaces-impl.jar
| richfaces-ui.jar servlet-api.jar
|
Do you see anything wrong?
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4114324#4114324
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4114324
More information about the jboss-user
mailing list