Filter does not work with *.jsp URL pattern???

Question

Hi All,
I am, by no means, very good at JSF or Java. I have looked at various forum posts on here for ways to implement a security filter to intercept requests to pages that first require one to be logged in, and if not, redirect them to the login page. Yes, I know a lot of you have heard this many times before, and I'm sorry to bring it up again.
BUT, from the guidance of other posts, I have got a filter that works fine when the url pattern is set to "/faces/*" or "/<anything>/*", however it won't work for "*.jsp" or "*.<anything>"
My filter is as follows:
package test.security;
import javax.faces.context.FacesContext;
import javax.servlet.Filter;
import javax.servlet.FilterChain;
import javax.servlet.FilterConfig;
import javax.servlet.http.HttpSession;
import javax.servlet.ServletRequest;
import javax.servlet.ServletResponse;
import javax.servlet.ServletException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
public class SecurityFilter implements Filter{
    /** Creates a new instance of SecurityFilter */
    private final static String FILTER_APPLIED = "_security_filter_applied";
    public SecurityFilter() {
    public void init(FilterConfig filterConfig) {
    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws java.io.IOException, ServletException{
        HttpServletRequest req = (HttpServletRequest)request;
        HttpServletResponse res = (HttpServletResponse)response;
        HttpSession session = req.getSession();
        String requestedPage = req.getPathTranslated();
        String user=null;
        if(request.getAttribute(FILTER_APPLIED) == null) {
            //check if the page requested is the login page or register page
            if((!requestedPage.endsWith("Page1.jsp")) /* This is the login page */
                //set the FILTER_APPLIED attribute to true
                request.setAttribute(FILTER_APPLIED, Boolean.TRUE);
                //Check that the session bean is not null and get the session bean property username.
                if(((test.SessionBean1)session.getAttribute("SessionBean1"))!=null) {
                    user = ((test.SessionBean1)session.getAttribute("SessionBean1")).getUsername();
                if((user==null)||(user.equals(""))) {
                   // try {
                 //       FacesContext.getCurrentInstance().getExternalContext().redirect("Page1.jsp");
                  //  } catch (ServletException ex) {
                  //      log("Error Description", ex);
                    res.sendRedirect("../Page1.jsp");
                    return;
        //deliver request to next filter
        chain.doFilter(request, response);
    public void destroy(){
}My web.xml declaration for the filter is:
<filter>
  <description>Filter to check whether user is logged in.</description>
  <filter-name>SecurityFilter</filter-name>
  <filter-class>test.security</filter-class>
</filter>
<filter-mapping>
  <filter-name>SecurityFilter</filter-name>
  <servlet-name>Faces Servlet</servlet-name>
</filter-mapping>
Note: I have also tried this with <url-pattern>*.jsp</url-pattern> for the filter mapping in place of the Faces Servlet
My web.xml declaration for the url pattern is:
<servlet-mapping>
  <servlet-name>Faces Servlet</servlet-name>
  <url-pattern>*.jsp</url-pattern>
</servlet-mapping>Which JSC/NetbeansVWP automatically creates a "JSCreator_index.jsp" which has:
<?xml version="1.0" encoding="UTF-8"?>
<jsp:root  version="1.2" xmlns:jsp="http://java.sun.com/JSP/Page">
  <jsp:forward page="Page1.jsp"/>
</jsp:root>When run, this causes an Error 500 in the browser and a NullPointerException in SecurityFilter.java on the line:
if((!requestedPage.endsWith("Page1.jsp")) /* This is the login page */I think I'm missing something that would be obvious to anyone who knows better than me. Any ideas?

Answer 1

Dear Ginger and Boris,
thanks for the information - the problem seems to ocur in EP7 as well, Boris told me it is fixed in SP15. We are on SP14 now, so there is hope !
actually the information in the oss note stated above is also true, as we have an Oracle DB. On a similar demo system (only difference is SQL DB) the hyphen search works !
best regards, thank you !
Johannes