Introspect whether setCharacterEncoding is present..

Hi..

How unadvicable would it be to introspect whether the setCharacterEncoding
is present on the Request object?

See, the problem is that we would like our application to be 2.2
compliant, but we'd love to use the setCharactherEncoding method if it is
available (>= 2.3 envs).

I am thinking that it is OK to simply introspect the Request object,
assuming that -every- servlet container on earth would give the -same-
type of Request object, and behave the same, even if the webapp specifies
2.2 in its web.xml file. However, I'm faced with some opposition, where
some feel that since it isn't specified in the spec, a >2.2 servlet
container would be smartest if it supplied an actual, complete servlet 2.2
environment to a 2.2 webapp, and thus either the setCharEnc wouldn't be
present (which actually wouldn't be problematic), or it would not behave
(which could be problematic).

What do you folks think/know?

Btw: where's all the folks at? Have a new "advanced" list been made?! ;)

Endre




------------------------ 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/