Good by me.
Thank you,
Martin Mulholland.
WebSphere Application Server Web Tier Architect
email: mmulholl_at_us.ibm.com
Shing Wai Chan <shing.wai.chan_at_oracle.com> wrote on 03/14/2017 01:27:04
PM:
> From: Shing Wai Chan <shing.wai.chan_at_oracle.com>
> To: jsr369-experts_at_servlet-spec.java.net
> Date: 03/14/2017 01:27 PM
> Subject: [servlet-spec users] [jsr369-experts] Re: request character
> encoding in web.xml (SERVLET_SPEC-161)
>
> Any comments on the renaming the xml elements defined lately
> from request-encoding/response-encoding to request-character-
> enocoding/response-character-encoding?
>
> Thanks.
> Shing Wai Chan
>
> > On Mar 9, 2017, at 11:43 AM, Shing Wai Chan
> <shing.wai.chan_at_oracle.com> wrote:
> >
> > In our previous discussion of
https://java.net/jira/browse/SERVLET_SPEC-161
> > ("Allow encoding to be set from deployment descriptor and API”),
> we decide to the following:
> >
> > a) add #get/setRequestCharacterEncoding and #get/
> setResponseCharacterEncoding in ServletContext
> > b) add <request-encoding>, <response-encoding> in web.xml
> >
> > Note that we have get/setCharacterEncoding in ServletRequest/
> ServletResponse, etc.
> > In other words, we have “characterEncoding” rather than just
> “Encoding" in our API.
> > If that is the case, then it is better to rename the new xml
> elements in web.xml as follows:
> > <request-character-encoding>
> > <response-character-encoding>
> >
> > Please let me know if you have any opinion.
> > Thanks.
> > Shing Wai Chan
> >
> >
>