Re: Introspect whether setCharacterEncoding is present..

Charles Forsythe <[email protected]> writes:

> I can imagine a "strict 2.2" mode that ignored the setCharacterEncoding 
> method on HttpRequest just for the sake of having one HttpRequest 
> implementation.  Why would such a mode have ANY implementation of 
> HttpServletRequestWrapper?  Why bother HAVING the Filter Wrapper classes 
> if they're non-functional?  Would they ever exists without the Filter 
> interfaces existing as well?  I just can't imagine why anyone would 
> implement a "2.2 pure" mode with such glaring impurities!
> 
> I think the Class.forName() test above should be a sufficient API level 
> test, or the Servlet Container is broken.

I think this is right.


-- 
Nic Ferrier
http://www.tapsellferrier.co.uk


------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/saFolB/TM
--------------------------------------------------------------------~-> 

Before posting a question, try to find your answer here: 
<http://www.egroups.com/links/advanced-servlets>
Announcements should go to: [email protected]
To Post a message, send it to: [email protected]
To Unsubscribe, send a blank message to: [email protected] 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/advanced-servlets/

<*> To unsubscribe from this group, send an email to:
    [email protected]

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/