"If needed" is a bit hard to define though, since this type of filter should never be needed if all else is working properly. Seam will then need a mechanism for setting the charset on a per page basis. Certainly can be done, but is non-trivial and opens a can of worms. If you specify web-app wide settings you get enhancement requests from folks needing to change the charset for a few pages. So you then provide an override mechanism (in pages.xml maybe). Then folks have more than just a few overrides, and don't want to have to (or can't) enumerate (think a large number of generated help files with MS encoding). Another enhancement for glob or regex matching.
I won't stop anyone from writing the best charset filter around. However I agree with the initial assessments. There are other ways to tell a browser what charset to use. Having a webapp wide filter can introduce complexity and bugs to those using these mechanisms (how is Seam going to be able to detect my meta tag?). Including this filter in the codebase as a utility is one thing. Enabling it by default is another. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3953068#3953068 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=3953068 Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ JBoss-user mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/jboss-user
