To maintain backward compatibility and consistency with the minimal
tomcat assembly (I only had this problem with Jetty) I think we need to
add Jasper & Jasper-Deployer into the assembly. I'll give it a try.
JSF is another story. It wasn't included in earlier minimal assemblies
so we're not regressing any function if we choose to not include it. I
don't have a strong opinion on it one way or the other.
Joe
David Jencks wrote:
ya, I think I figured "minimal" meant "no jsps" which no one except greg
wilkins might agree with :-). How about jsf?
(maybe I'm exaggerating his distaste for jsps)
for jsps we need to add the jasper and jasper-builder configs.
for jsf we need to add myfaces and myfaces-builder configs.
the builder configs need to be loaded, the others can have load="false":
any such config needs to be in the pom (yes, I had to build the
tomcat-ee config about 4-6 times while I sorted out which went where)
thanks
david jencks
On Apr 2, 2007, at 2:36 PM, Joe Bohn wrote:
Joe Bohn wrote:
geronimo-jetty6-minimal:
- Deploying a simple JSP war resulted in an UnavailableException for
org.apache.jasper.servlet.JspServlet from the application classloader
and failures attempting to start the GBean. I'll open a JIRA for
this issue. I suspect that we're not including the correct jasper
item in the classloader of the web app. I think we can push this
milestone out even with this error given that people can work with
the jetty and the jee5 assembly until this issue is resolved in a
subsequent milestone.
Created https://issues.apache.org/jira/browse/GERONIMO-3057
Joe
