didn't ignore you, I'm just quite busy this week. Actually the test suite should be deployable without any modifications. Having said this it is quite embarassing having to admit you're right that it isn't. It seems to have been released without proper testing of the packaged war. We're going to reconsider our release strategy... I won't get around to correcting this until next week. We're planning to release 3.0.0 RC1 by the end of next week, and be assured that it's test suite will work out of the box.
Regards,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Well, actually it wasn't a real mistake in the testsuite, as I must admint - quite embarassed. :)
That NullPointerException occurs when there's no FacesContext available. This can have different reasons. One is misconfiguration (JSF isn't setup properly). The other is calling a JSP that should be called via JSF directly.
In the testsuite, JSF is mapped to /faces/* - so every JSP (except for /index.jsp which is a redirect to /faces/jsf/index.jsp) must be called with the /faces/ prefix. When you call /jsf/index.jsp directly, you'll get the NullPointerException since it bypasses FacesServlet. When you call /faces/jsf/index.jsp, it'll be handled by FacesServlet and there'll be a FacesContext available and everything should work fine.
HTH,
Thomas
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Should I be able to run M3 with tomcat 5.5.15 out of the box? I am getting the following:
org.apache.jasper.JasperException: Exception in JSP: /index.jsp:4
1: <%@ taglib uri="http://java.sun.com/jsf/html" prefix="h" %>
2: <%@ taglib uri="http://java.sun.com/jsf/core" prefix="f" %>
3:
4: <f:view>
5: <html>
6: <head>
7: <title><h:outputText value="JSF-Spring Testsuite"/></title>
Stacktrace:
org.apache.jasper.servlet.JspServletWrapper.handleJspException(JspServletWrapper.java:504)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:393)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
root cause
java.lang.NullPointerException
javax.faces.webapp.UIComponentTag.setupResponseWriter(UIComponentTag.java:615)
javax.faces.webapp.UIComponentTag.doStartTag(UIComponentTag.java:217)
org.apache.myfaces.taglib.core.ViewTag.doStartTag(ViewTag.java:71)
org.apache.jsp.index_jsp._jspx_meth_f_view_0(org.apache.jsp.index_jsp:88)
org.apache.jsp.index_jsp._jspService(org.apache.jsp.index_jsp:64)
org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:332)
org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)
Thanks
Hi Steve,
didn't ignore you, I'm just quite busy this week. Actually the test suite should be deployable without any modifications. Having said this it is quite embarassing having to admit you're right that it isn't. It seems to have been released without proper testing of the packaged war. We're going to reconsider our release strategy... I won't get around to correcting this until next week. We're planning to release 3.0.0 RC1 by the end of next week, and be assured that it's test suite will work out of the box.
Regards,
Thomas
Hello Thomas,
I'm developing an application with 3.0.0 RC1 release of your framework and I´m having a NullPointerException like that one in the other post.
I would like to know, if it's possible, what have you done to fix the testsuite from 3.0.0 M3.
Thanks a lot.
Regards. Angel
Well, actually it wasn't a real mistake in the testsuite, as I must admint - quite embarassed. :)
That NullPointerException occurs when there's no FacesContext available. This can have different reasons. One is misconfiguration (JSF isn't setup properly). The other is calling a JSP that should be called via JSF directly.
In the testsuite, JSF is mapped to /faces/* - so every JSP (except for /index.jsp which is a redirect to /faces/jsf/index.jsp) must be called with the /faces/ prefix. When you call /jsf/index.jsp directly, you'll get the NullPointerException since it bypasses FacesServlet. When you call /faces/jsf/index.jsp, it'll be handled by FacesServlet and there'll be a FacesContext available and everything should work fine.
HTH,
Thomas