ICEfaces
  1. ICEfaces
  2. ICE-3872

implement setCharacterEncoding on underlying request

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Invalid
    • Affects Version/s: 1.8DR#1
    • Fix Version/s: None
    • Component/s: Framework
    • Labels:
      None
    • Environment:
      icefaces

      Description


      The standard ExternalContext is implemented as follows:

          public void setRequestCharacterEncoding(String encoding) throws UnsupportedEncodingException {
              request.setCharacterEncoding(encoding);
          }

      currently BridgeExternalContext is a no-op for this (ICE-3851 ) as the character encoding of the Ajax response is not meaningfully under application control. There may be an interpretation of it that is useful to the application, however.

        Activity

        Hide
        Ken Fyten added a comment -

        Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup.

        Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf

        If the issue persists with the current ICEfaces release, please create a new JIRA for it.

        Show
        Ken Fyten added a comment - Marking as Closed / Invalid as part of legacy ICEfaces 1.x, 2.x JIRA cleanup. Note: This issue may be resolved in a newer ICEfaces release, available here: http://www.icesoft.org/java/downloads/icefaces-downloads.jsf If the issue persists with the current ICEfaces release, please create a new JIRA for it.

          People

          • Assignee:
            Unassigned
            Reporter:
            Ted Goddard
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: