[jboss-user] [JBoss Seam] - Registration example not working with SEAM-2.0.0.BETA1 and A
Hi!
I just downloaded and extracted:
JBoss Application Server 4.2.1.GA
and
JBoss SEAM 2.0.0.BETA1
then I tried running the test for example/registration:
cd examples/registration
ant testexample
I get the following error:
[testng] [Parser] Running:
|[testng]
/Users/thomas/dev/jboss-seam-2.0.0.BETA1/examples/registration/src/org/jboss/seam/example/registration/test/testng.xml
|
|[testng] WARN 20-08 15:40:50,885
[org.jboss.mx.loading.UnifiedLoaderRepository3.addClassLoader():675] Tried to
add non-URLClassLoader. Ignored
|[testng] INFO 20-08 15:40:54,196
[com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():126]
JBossTS Transaction Service (JTA version) - JBoss Inc.
|[testng] INFO 20-08 15:40:54,205
[com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():128]
Setting up property manager MBean and JMX layer
|[testng] WARN 20-08 15:40:54,399
[com.arjuna.ats.arjuna.coordinator.TxControl.():266]
[com.arjuna.ats.arjuna.coordinator.TxControl_1] - Name of XA node not defined.
Using -53edfeca:c11e:46c999e6:0
|[testng] INFO 20-08 15:40:54,576
[com.arjuna.ats.arjuna.recovery.TransactionStatusManager.addService():110]
[com.arjuna.ats.arjuna.recovery.TransactionStatusManager_1] - Starting service
com.arjuna.ats.arjuna.recovery.ActionStatusService on port 49438
|[testng] INFO 20-08 15:40:54,604 [?.?():?] TransactionStatusManagerItem
- host: 172.18.1.54 port: 49438
|[testng] INFO 20-08 15:40:54,648
[com.arjuna.ats.arjuna.recovery.TransactionStatusManager.start():161]
[com.arjuna.ats.arjuna.recovery.TransactionStatusManager_3] -
TransactionStatusManager started on port 49438 with service
com.arjuna.ats.arjuna.recovery.ActionStatusService
|[testng] INFO 20-08 15:40:54,693 [?.?():?] Registering mbean for module
'arjuna'
|[testng] INFO 20-08 15:40:54,712 [?.?():?] Initialising JMX agent
com.arjuna.ats.internal.jbossatx.agent.LocalJBossAgentImpl
|[testng] INFO 20-08 15:40:54,792
[com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():163]
Starting recovery manager
|[testng] INFO 20-08 15:40:54,848 [?.?():?]
|[testng] --- Start RecoveryActivators
|[testng] INFO 20-08 15:40:54,895
[com.arjuna.ats.internal.arjuna.recovery.RecoveryManagerImple.():142]
[com.arjuna.ats.internal.arjuna.recovery.ready] RecoveryManagerImple is ready
on port 49.439
|[testng] INFO 20-08 15:40:54,898
[com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():168]
Recovery manager started
|[testng] INFO 20-08 15:40:54,906
[com.arjuna.ats.jbossatx.jta.TransactionManagerService.startService():191]
Binding TransactionManager JNDI Reference
|[testng] INFO 20-08 15:41:01,836
[org.jboss.jms.server.ServerPeer.():187] ServerPeer[0] creating server
peer with ID 0
|[testng] FAILED CONFIGURATION: @BeforeClass init
|[testng] org.jboss.deployers.spi.IncompleteDeploymentException: Summary
of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
|
|[testng] *** CONTEXTS MISSING DEPENDENCIES: Name -> Dependency{Required
State:Actual State}
|
|[testng] jboss.jca:name=DefaultDS,service=DataSourceBinding
|[testng] ->
jboss.jca:name=DefaultDS,service=LocalTxCM{Create:Configured}
|[testng] -> jboss.jca:name=DefaultDS,service=LocalTxCM{Start:Configured}
|
|[testng] jboss.jca:name=DefaultDS,service=LocalTxCM
|[testng] ->
jboss.jca:name=DefaultDS,service=ManagedConnectionPool{Create:Configured}
|[testng] ->
jboss.jca:name=DefaultDS,service=ManagedConnectionPool{Start:Configured}
|
|[testng] jboss.jca:name=DefaultDS,service=ManagedConnectionFactory
|[testng] ->
jboss.jca:name='jboss-local-jdbc.rar',service=RARDeployment{Start:** NOT FOUND
**}
|[testng] ->
jboss.jca:name='jboss-local-jdbc.rar',service=RARDeployment{Create:** NOT FOUND
**}
|
|[testng] jboss.jca:name=DefaultDS,service=ManagedConnectionPool
|[testng] ->
jboss.jca:name=DefaultDS,service=ManagedConnectionFactory{Create:Configured}
|[testng] ->
jboss.jca:name=DefaultDS,service=ManagedConnectionFactory{Start:Configured}
|
|[testng] jboss.jca:name=JmsXA,service=DataSourceBinding
|[testng] -> jboss.jca:name=JmsXA,service=TxCM{Start:Configured}
|[testng] -> jboss.jca:name=JmsXA,service=TxCM{Create:Configured}
|
|[testng] jboss.jca:name=JmsXA,service=ManagedConnectionFactory
|[testng] -> jboss.jca:name='jms-ra.rar',service=RARDeployment{Create:**
NOT FOUND **}
|[testng] -> jboss.messaging:service=ServerPeer{Start:Configured}
|[testng] -> jboss.jca:name='jms-ra.rar',service=RARDeployment{Start:**
NOT FOUND **}
|[testng] -> jboss.messaging:service=ServerPeer{Create:Configured}
|
|[testng] jboss.jca:name=JmsXA,service=ManagedConnectionPool
|[testng] ->
jboss.jca:name=JmsXA,service=ManagedConnectionFactory{Start
[jboss-user] [JBoss Seam] - registration example not working
Hi. I tried out few seam examples, and all the ones i tried worked fine except the "registration" example which is the one i really need to work so i can start learning, since it is the simplest one. I am using JDK 1.6.0 (b105) Tomcat 6.0.9, seam 1.1.6 GA. can anyone tell me what i am missing? Here is what i get when i visit the url of that example: HTTP Status 500 - type Exception report message description The server encountered an internal error () that prevented it from fulfilling this request. exception javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/jasper/servlet/JasperLoader) of the current class, org/apache/jsp/register_jspx, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature javax.faces.webapp.FacesServlet.service(FacesServlet.java:152) root cause javax.faces.FacesException: java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/jasper/servlet/JasperLoader) of the current class, org/apache/jsp/register_jspx, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:422) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234) org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:59) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) root cause javax.servlet.ServletException: java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/jasper/servlet/JasperLoader) of the current class, org/apache/jsp/register_jspx, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature org.apache.jasper.servlet.JspServlet.service(JspServlet.java:274) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:416) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234) org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:59) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) root cause java.lang.LinkageError: loader constraint violation: when resolving interface method "javax.servlet.jsp.JspApplicationContext.getExpressionFactory()Ljavax/el/ExpressionFactory;" the class loader (instance of org/apache/jasper/servlet/JasperLoader) of the current class, org/apache/jsp/register_jspx, and the class loader (instance of org/apache/catalina/loader/StandardClassLoader) for resolved class, javax/servlet/jsp/JspApplicationContext, have different Class objects for the type javax/el/ExpressionFactory used in the signature org.apache.jsp.register_jspx._jspInit(register_jspx.java:35) org.apache.jasper.runtime.HttpJspBase.init(HttpJspBase.java:80) org.apache.jasper.servlet.JspServletWrapper.getServlet(JspServletWrapper.java:157) org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:320) org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:320) org.apache.jasper.servlet.JspServlet.service(JspServlet.java:266) javax.servlet.http.HttpServlet.service(HttpServlet.java:803) org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(ServletExternalContextImpl.java:416) org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHandlerImpl.java:234) org.jboss.seam.jsf.SeamViewHandler.renderView(SeamViewHandler.java:59) org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:384) javax.faces.webapp.FacesServlet.service(FacesServlet.java:138) note The full stack trace of the root cause is available in
