[
http://jira.jboss.com/jira/browse/JBSEAM-1265?page=comments#action_12360880 ]
Michael Youngstrom commented on JBSEAM-1265:
--------------------------------------------
So, I was able to get around the exception by simply removing the tomcat specific piece of
code in JBossELInstaller.
It appears that the this piece of code will need to be refactored anyway in order for seam
to work with other JSP 2.1 containers since it's method of finding the container's
current ExpressionFactory is kind of tomcat specific. It would be nice if this piece of
code could be made a little more generic so that if a JSP 2.1 container is not available
then no attempt is made to wrap the containers ExpressionFactory.
Mike
Dependency on Jsp 2.1 in HEAD JspApplicationContext referenced in
JBossELInstaller
----------------------------------------------------------------------------------
Key: JBSEAM-1265
URL:
http://jira.jboss.com/jira/browse/JBSEAM-1265
Project: JBoss Seam
Issue Type: Bug
Components: Core
Affects Versions: 1.2.1.GA
Reporter: Michael Youngstrom
Priority: Blocker
Fix For: 1.3.0.BETA1
When I attempt to run the latest from head as of the date of this issue in tomcat 5.5 I
get a class not found error for JspApplicationContext.
The problem appears to be in JBossELInstaller.
Note I'm running the IBM JDK.
java.lang.NoClassDefFoundError: javax.servlet.jsp.JspApplicationContext
at java.lang.J9VMInternals.verifyImpl(Native Method)
at java.lang.J9VMInternals.verify(J9VMInternals.java:63)
at java.lang.J9VMInternals.initialize(J9VMInternals.java:124)
at java.lang.Class.newInstanceImpl(Native Method)
at java.lang.Class.newInstance(Class.java:1301)
at org.jboss.seam.Component.instantiateJavaBean(Component.java:1133)
at org.jboss.seam.Component.instantiate(Component.java:1089)
at org.jboss.seam.Component.newInstance(Component.java:1740)
at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:184)
at org.jboss.seam.contexts.Lifecycle.startup(Lifecycle.java:161)
at org.jboss.seam.contexts.Lifecycle.endInitialization(Lifecycle.java:136)
at org.jboss.seam.init.Initialization.init(Initialization.java:500)
at org.jboss.seam.servlet.SeamListener.contextInitialized(SeamListener.java:33)
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3764)
at org.apache.catalina.core.StandardContext.start(StandardContext.java:4216)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at org.apache.catalina.core.StandardHost.start(StandardHost.java:736)
at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1014)
at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443)
at org.apache.catalina.core.StandardService.start(StandardService.java:448)
at org.apache.catalina.core.StandardServer.start(StandardServer.java:700)
at org.apache.catalina.startup.Catalina.start(Catalina.java:552)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:64)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:615)
at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:295)
at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:433)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira