-
1. Re: Web.xml not accepting <dispatcher>
massep Mar 27, 2008 1:48 PM (in response to massep)Some text did not show up in my post....
The tags not accepted are:<dispatcher>REQUEST</dispatcher> <dispatcher>FORWARD</dispatcher> <dispatcher>INCLUDE</dispatcher> </filter-mapping>
-
2. Re: Web.xml not accepting <dispatcher>
mail.micke Mar 27, 2008 1:56 PM (in response to massep)It isn't in the 2.3 DTD
http://java.sun.com/dtd/web-app_2_3.dtd
Can you switch to version 2.4 ?
Don't know if will be a problem or not, but I use ajax4jsf via Seam (don't have to setup the filter mapping) with a non 2.4 web.xml without problems. -
3. Re: Web.xml not accepting <dispatcher>
massep Mar 27, 2008 2:19 PM (in response to massep)I'll look into upgrading the servlet container to 2.4.
But I'd rather not have to do that.
I originally ask the question because of weird things happening in IE7.
Everything I've done with richfaces until now is working fine in FF2 and IE6 but not in IE7.
For example, a calendar button works only when I'm navigating to that page from a page that has some richfaces controls but not when I'm navigating from a page that does not. The javascript error I get is 'Calendar ' is undefined.
Same thing happens with tabpanel, the stylesheet isn't applied and none of the javascript executes. I get a javascript error that says 'RichFaces' is undefined. But if I navigate to a page that has richfaces control on it and then navigate back to the page with the tabpanel, everything is fine.
My JSF is configured for Client state saving and most of my navigation is forwarded.
Thanks -
4. Re: Web.xml not accepting '<dispatcher>'
massep Mar 27, 2008 3:15 PM (in response to massep)I switched from 2.3 to 2.4 and see no differences.
Cheers