1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Todd Patrick



I downloaded 1.1.3 
Nightly build and I am trying to configure my web.xml file as 
such:

?xml version="1.0" encoding="UTF-8"?web-app 
version="2.4" xmlns="http://java.sun.com/xml/ns/j2ee" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee 
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd" 
context-param 
param-namecom.sun.faces.verifyObjects/param-name 
param-valuetrue/param-value 
/context-param 
context-param 
param-namecom.sun.faces.validateXml/param-name 
param-valuetrue/param-value 
/context-param 
context-param 
param-namejavax.faces.CONFIG_FILES/param-name 
param-value/WEB-INF/faces-config.xml/param-value 
/context-param 
context-param 
param-namejavax.faces.STATE_SAVING_METHOD/param-name 
param-valueclient/param-value 
/context-param 
context-param 
param-nameorg.apache.myfaces.CHECK_EXTENSIONS_FILTER/param-name 
param-valuefalse/param-value 
/context-param 
servlet 
servlet-nameFaces 
Servlet/servlet-name 
servlet-classjavax.faces.webapp.FacesServlet/servlet-class 
load-on-startup1/load-on-startup 
/servlet 
servlet-mapping 
servlet-nameFaces 
Servlet/servlet-name 
url-pattern/transactionbrowser/*/url-pattern 
/servlet-mapping 
session-config 
session-timeout 
30 
/session-timeout 
/session-config 
welcome-file-list 
welcome-file 
index.jsp 
/welcome-file 
/welcome-file-list !-- Extensions Filter 
-- 
filter 
filter-nameMyFacesExtensionsFilter/filter-name 
filter-classorg.apache.myfaces.webapp.filter.ExtensionsFilter/filter-class 
init-param 
param-namemaxFileSize/param-name 
param-value20m/param-value 
/init-param /filter 
filter-mapping 
filter-nameMyFacesExtensionsFilter/filter-name 
servlet-nameFaces Servlet/servlet-name 
/filter-mapping 
filter-mapping 
filter-nameMyFacesExtensionsFilter/filter-name 
url-pattern/transactionbrowser/*/url-pattern 
/filter-mapping/web-app


However, I keep 
receiving the error message:

java.lang.IllegalStateException: ExtensionsFilter not correctly 
configured. JSF mapping missing. JSF pages not covered. Please see: http://myfaces.apache.org/tomahawk/extensionsFilter.html


I found a similar 
thread about 1.1.2, however how do I fix this issue in 
1.1.3?

I am using Sun Java 
System Application Server 8.2

Thanks,

--Todd


Re: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Mike Kienenberger

On 5/4/06, Todd Patrick [EMAIL PROTECTED] wrote:


I downloaded 1.1.3 Nightly build and I am trying to configure my web.xml
file as such:

?xml version=1.0 encoding=UTF-8?
web-app version=2.4 xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
context-param
param-namecom.sun.faces.verifyObjects/param-name
param-valuetrue/param-value
/context-param
context-param
param-namecom.sun.faces.validateXml/param-name
param-valuetrue/param-value
/context-param
context-param
param-namejavax.faces.CONFIG_FILES/param-name
param-value/WEB-INF/faces-config.xml/param-value
/context-param
context-param
param-namejavax.faces.STATE_SAVING_METHOD/param-name
param-valueclient/param-value
/context-param
context-param

param-nameorg.apache.myfaces.CHECK_EXTENSIONS_FILTER/param-name
param-valuefalse/param-value
/context-param
servlet
servlet-nameFaces Servlet/servlet-name
servlet-classjavax.faces.webapp.FacesServlet/servlet-class
load-on-startup1/load-on-startup
/servlet
servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/transactionbrowser/*/url-pattern
/servlet-mapping
session-config
session-timeout
30
/session-timeout
/session-config
welcome-file-list
welcome-file
index.jsp
/welcome-file
/welcome-file-list
!-- Extensions Filter --
filter
filter-nameMyFacesExtensionsFilter/filter-name

filter-classorg.apache.myfaces.webapp.filter.ExtensionsFilter/filter-class
init-param
param-namemaxFileSize/param-name
param-value20m/param-value
/init-param
/filter
filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
servlet-nameFaces Servlet/servlet-name
/filter-mapping
filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
url-pattern/transactionbrowser/*/url-pattern
/filter-mapping
/web-app



However, I keep receiving the error message:

java.lang.IllegalStateException: ExtensionsFilter not correctly configured.
JSF mapping missing. JSF pages not covered. Please see:
http://myfaces.apache.org/tomahawk/extensionsFilter.html


I found a similar thread about 1.1.2, however how do I fix this issue in
1.1.3?


Follow the link given :)

Basically, you've double-configured the part that modifies your JSF
pages, but haven't configured the part that serves independent
resources.

Delete this one:


filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
url-pattern/transactionbrowser/*/url-pattern
/filter-mapping


And add in the one on the web page.


RE: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Todd Patrick
Thank you for the suggestion!

This didn't work either... The error keeps saying:

java.lang.IllegalStateException: ExtensionsFilter not correctly
configured. JSF mapping missing. JSF pages not covered. Please see:
http://myfaces.apache.org/tomahawk/extensionsFilter.html

I even tried to add:
 
filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
  url-pattern*.jsf/url-pattern
/filter-mapping

That's didn't work either.

?xml version=1.0 encoding=UTF-8?
web-app version=2.4 xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
context-param
param-namecom.sun.faces.verifyObjects/param-name
param-valuetrue/param-value
/context-param
context-param
param-namecom.sun.faces.validateXml/param-name
param-valuetrue/param-value
/context-param
context-param
param-namejavax.faces.CONFIG_FILES/param-name
param-value/WEB-INF/faces-config.xml/param-value
/context-param
context-param
param-namejavax.faces.STATE_SAVING_METHOD/param-name
param-valueclient/param-value
/context-param
servlet
servlet-nameFaces Servlet/servlet-name
servlet-classjavax.faces.webapp.FacesServlet/servlet-class
load-on-startup1/load-on-startup
/servlet
servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/transactionbrowser/*/url-pattern
/servlet-mapping
session-config
session-timeout
30
/session-timeout
/session-config
welcome-file-list
welcome-file
index.jsp
/welcome-file
/welcome-file-list
!-- Extensions Filter --
filter
filter-nameMyFacesExtensionsFilter/filter-name
 
filter-classorg.apache.myfaces.webapp.filter.ExtensionsFilter/filter-
class
init-param
param-namemaxFileSize/param-name
param-value20m/param-value
/init-param
/filter
filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
servlet-nameFaces Servlet/servlet-name
/filter-mapping
filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
url-pattern/myFacesExtensionResource/*/url-pattern
/filter-mapping
/web-app


Thanks,

--Todd

-Original Message-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 04, 2006 2:57 PM
To: MyFaces Discussion
Subject: Re: 1.1.3 returns the error: java.lang.IllegalStateException:
ExtensionsFilter not correctly configured. JSF mapping missing. JSF
pages not covered.

On 5/4/06, Todd Patrick [EMAIL PROTECTED] wrote:
 url-pattern/transactionbrowser/myFacesExtensionResource/*/url-patte
 rn

No, it's

url-pattern/myFacesExtensionResource/*/url-pattern


Re: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Mario Ivankovits
Todd Patrick schrieb:
  
 url-pattern/transactionbrowser/myFacesExtensionResource/*/url-pattern
   
No, its

/faces/myFacesExtensionResource/*

as stated in the documentation. The url-pattern will always be relative to the 
context.

Ciao,
Mario




RE: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Todd Patrick
Thank you, I tired that as well.

Is there a bug in the 1.1.3 nightly build?

Thanks,

--Todd

-Original Message-
From: Mario Ivankovits [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 04, 2006 3:09 PM
To: MyFaces Discussion
Subject: Re: 1.1.3 returns the error: java.lang.IllegalStateException:
ExtensionsFilter not correctly configured. JSF mapping missing. JSF
pages not covered.

Todd Patrick schrieb:
  
 url-pattern/transactionbrowser/myFacesExtensionResource/*/url-patte
 rn
   
No, its

/faces/myFacesExtensionResource/*

as stated in the documentation. The url-pattern will always be relative
to the context.

Ciao,
Mario




Re: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Mike Kienenberger

You're making it harder than it has to be :)

There are two required mappings.

One has to be absolute and has to look exactly like this.  It should
probably be your first filter-mapping for performance reasons.   (I
had assumed you'd copied it verbatim, but I see that's now not the
case).

!-- extension mapping for serving page-independent resources
(javascript, stylesheets, images, etc.)  --
filter-mapping
   filter-nameMyFacesExtensionsFilter/filter-name
   url-pattern/faces/myFacesExtensionResource/*/url-pattern
/filter-mapping

The second mapping must match your Faces servlet mapping.

The easiest way to do that is to use:

!-- extension mapping for adding script/, link/, and other
resource tags to JSF-pages  --
filter-mapping
   filter-nameMyFacesExtensionsFilter/filter-name
   !-- servlet-name must match the name of your
javax.faces.webapp.FacesServlet entry --
   servlet-nameFaces Servlet/servlet-name
/filter-mapping


Your best bet is to literally copy these settings from the web page
and add them to your web.xml file exactly as they appear.   As long as
your servlet name and facelets name are the same elsewhere (which they
appear to be), that's all that's required.


RE: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Todd Patrick
Is it a problem that my Faces servlet mapping is:

servlet
servlet-nameFaces Servlet/servlet-name
servlet-classjavax.faces.webapp.FacesServlet/servlet-class
load-on-startup1/load-on-startup
/servlet
servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/transactionbrowser/*/url-pattern
/servlet-mapping

Should it be?:

   servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern*.jsf/url-pattern
/servlet-mapping

I need to read up on servlet-mappings.

Thanks,

--Todd

-Original Message-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 04, 2006 3:15 PM
To: MyFaces Discussion
Subject: Re: 1.1.3 returns the error: java.lang.IllegalStateException:
ExtensionsFilter not correctly configured. JSF mapping missing. JSF
pages not covered.

You're making it harder than it has to be :)

There are two required mappings.

One has to be absolute and has to look exactly like this.  It should
probably be your first filter-mapping for performance reasons.   (I
had assumed you'd copied it verbatim, but I see that's now not the
case).

!-- extension mapping for serving page-independent resources
(javascript, stylesheets, images, etc.)  -- filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
url-pattern/faces/myFacesExtensionResource/*/url-pattern
/filter-mapping

The second mapping must match your Faces servlet mapping.

The easiest way to do that is to use:

!-- extension mapping for adding script/, link/, and other resource
tags to JSF-pages  -- filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
!-- servlet-name must match the name of your
javax.faces.webapp.FacesServlet entry --
servlet-nameFaces Servlet/servlet-name /filter-mapping


Your best bet is to literally copy these settings from the web page
and add them to your web.xml file exactly as they appear.   As long as
your servlet name and facelets name are the same elsewhere (which they
appear to be), that's all that's required.


Re: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Mike Kienenberger

On 5/4/06, Todd Patrick [EMAIL PROTECTED] wrote:

Is it a problem that my Faces servlet mapping is:
url-pattern/transactionbrowser/*/url-pattern

[vs]

url-pattern*.jsf/url-pattern



No, the beauty of using a servlet-name filter mapping is that it
doesn't matter how you specify your servlet mapping.   And changes to
your servlet mapping are automatically picked up by the filter
mapping.


filter-nameMyFacesExtensionsFilter/filter-name
javax.faces.webapp.FacesServlet entry --
servlet-nameFaces Servlet/servlet-name /filter-mapping


RE: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Todd Patrick
This is so frustrating... I really appreciate your help.

These changes still are unsuccessful, I've tried each suggestion and
Googled on the topic as well with no success.

My web.xml file is now:

?xml version=1.0 encoding=UTF-8?
web-app version=2.4 xmlns=http://java.sun.com/xml/ns/j2ee;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee
http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd;
context-param
param-namecom.sun.faces.verifyObjects/param-name
param-valuetrue/param-value
/context-param
context-param
param-namecom.sun.faces.validateXml/param-name
param-valuetrue/param-value
/context-param
context-param
param-namejavax.faces.CONFIG_FILES/param-name
param-value/WEB-INF/faces-config.xml/param-value
/context-param
context-param
param-namejavax.faces.STATE_SAVING_METHOD/param-name
param-valueclient/param-value
/context-param
servlet
servlet-nameFaces Servlet/servlet-name
servlet-classjavax.faces.webapp.FacesServlet/servlet-class
load-on-startup1/load-on-startup
/servlet
servlet-mapping
servlet-nameFaces Servlet/servlet-name
url-pattern/transactionbrowser/*/url-pattern
/servlet-mapping
session-config
session-timeout
30
/session-timeout
/session-config
welcome-file-list
welcome-file
index.jsp
/welcome-file
/welcome-file-list
!-- Extensions Filter --
filter
filter-nameMyFacesExtensionsFilter/filter-name
 
filter-classorg.apache.myfaces.webapp.filter.ExtensionsFilter/filter-
class
init-param
param-namemaxFileSize/param-name
param-value20m/param-value
/init-param
/filter
filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
url-pattern/faces/myFacesExtensionResource/*/url-pattern
/filter-mapping
filter-mapping
filter-nameMyFacesExtensionsFilter/filter-name
servlet-nameFaces Servlet/servlet-name
/filter-mapping
/web-app


Thanks,

--Todd 

-Original Message-
From: Mike Kienenberger [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 04, 2006 3:27 PM
To: MyFaces Discussion
Subject: Re: 1.1.3 returns the error: java.lang.IllegalStateException:
ExtensionsFilter not correctly configured. JSF mapping missing. JSF
pages not covered.

On 5/4/06, Todd Patrick [EMAIL PROTECTED] wrote:
 Is it a problem that my Faces servlet mapping is:
 url-pattern/transactionbrowser/*/url-pattern
[vs]
 url-pattern*.jsf/url-pattern


No, the beauty of using a servlet-name filter mapping is that it
doesn't matter how you specify your servlet mapping.   And changes to
your servlet mapping are automatically picked up by the filter mapping.

 filter-nameMyFacesExtensionsFilter/filter-name
 javax.faces.webapp.FacesServlet entry --
 servlet-nameFaces Servlet/servlet-name /filter-mapping


Re: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Mario Ivankovits
Hi Todd!
 Is it a problem that my Faces servlet mapping is:
   
Regardless of what your servlet mapping will be, the extensions filter
(and the url-pattern) has to be as stated by the documentation or by
mike. So NOT using your /transactionbrowser/* but /faces/

If this failes, the best will be to install the myfaces sources and put
a breakpoint at the exception source to see what happens.
It isnt that complicated :-)

Ciao,
Mario



Re: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Mario Ivankovits
Hi Todd!
 context-param

 param-nameorg.apache.myfaces.CHECK_EXTENSIONS_FILTER/param-name
 param-valuefalse/param-value
 /context-param

Given that you already told the system to disable this filter check I
bet that the web.xml you edit is not the used by tomcat. Just a wild
guess, dont get it personal :-) - its something happend here now and
then when the deployment didnt do what I expected it to do.
Do you use somethink like a exploded tomcat directory, or a
eclipse/idea whatever automatic deployment?
If so, please look at the exploded web.xml.

Ciao,
Mario



RE: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Todd Patrick
Thank you, I looked at that as well...

Would you provide an example of how you set-up your web.xml file?

Thanks,

--Todd 

-Original Message-
From: Mario Ivankovits [mailto:[EMAIL PROTECTED] 
Sent: Thursday, May 04, 2006 3:47 PM
To: MyFaces Discussion
Subject: Re: 1.1.3 returns the error: java.lang.IllegalStateException:
ExtensionsFilter not correctly configured. JSF mapping missing. JSF
pages not covered.

Hi Todd!
 context-param

 param-nameorg.apache.myfaces.CHECK_EXTENSIONS_FILTER/param-name
 param-valuefalse/param-value
 /context-param

Given that you already told the system to disable this filter check I
bet that the web.xml you edit is not the used by tomcat. Just a wild
guess, dont get it personal :-) - its something happend here now and
then when the deployment didnt do what I expected it to do.
Do you use somethink like a exploded tomcat directory, or a
eclipse/idea whatever automatic deployment?
If so, please look at the exploded web.xml.

Ciao,
Mario



Re: 1.1.3 returns the error: java.lang.IllegalStateException: ExtensionsFilter not correctly configured. JSF mapping missing. JSF pages not covered.

2006-05-04 Thread Mike Kienenberger

On 5/4/06, Todd Patrick [EMAIL PROTECTED] wrote:

Would you provide an example of how you set-up your web.xml file?


One other thing you might check is to be sure you've got things in the
correct order in your web.xml file.filters, filter-mappings,
listeners, servlets, servlet-mappings.

   context-param
   param-nameorg.apache.myfaces.CHECK_EXTENSIONS_FILTER/param-name
   param-valuetrue/param-value
   /context-param

[...]

  filter
filter-nameMyFacesExtensionsFilter/filter-name

filter-classorg.apache.myfaces.webapp.filter.ExtensionsFilter/filter-class
init-param
  param-nameuploadMaxFileSize/param-name
  param-value100m/param-value
  descriptionSet the size limit for uploaded files.
  Format: 10 - 10 bytes
  10k - 10 KB
  10m - 10 MB
  1g - 1 GB
  /description
  /init-param
  init-param
  param-nameuploadThresholdSize/param-name
  param-value100k/param-value
  descriptionSet the threshold size - files
  below this limit are stored in memory, files above
  this limit are stored on disk.

  Format: 10 - 10 bytes
  10k - 10 KB
  10m - 10 MB
  1g - 1 GB
  /description
  /init-param
  /filter

[...]

   !-- extension mapping for serving page-independent resources
(javascript, stylesheets, images, etc.)  --
   filter-mapping
 filter-nameMyFacesExtensionsFilter/filter-name
 url-pattern/faces/myFacesExtensionResource/*/url-pattern
   /filter-mapping

[...]

   !-- extension mapping for adding script/, link/, and other
resource tags to JSF-pages  --
   filter-mapping
 filter-nameMyFacesExtensionsFilter/filter-name
 !-- servlet-name must match the name of your
javax.faces.webapp.FacesServlet entry --
 servlet-nameFacesServlet/servlet-name
   /filter-mapping

[...]

   listener
   
listener-classorg.apache.myfaces.webapp.StartupServletContextListener/listener-class
   /listener

[...]

   servlet
   servlet-nameFacesServlet/servlet-name
   servlet-classjavax.faces.webapp.FacesServlet/servlet-class
   load-on-startup1/load-on-startup
   /servlet

   servlet-mapping
   servlet-nameFacesServlet/servlet-name
   url-pattern/faces/*/url-pattern
   /servlet-mapping