ICEfaces
  1. ICEfaces
  2. ICE-5679

Standardize how ICEfaces detects and uses encoding

          Details

          • Type: Improvement Improvement
          • Status: Closed
          • Priority: Major Major
          • Resolution: Fixed
          • Affects Version/s: 2.0-Alpha2
          • Fix Version/s: 2.0-Beta1, 2.0.0
          • Component/s: Framework
          • Labels:
            None
          • Environment:
            ICEfaces 2 JSF 2
          • Affects:
            Compatibility/Configuration

            Description

            We currently have encoding defaulting to UTF-8 which covers a large number of our cases but we need to detect and use the proper encoding for a page.

              Issue Links

              blocks

              Bug - A problem which impairs or prevents the functions of the product. ICE-5608 Chinese characters display improperly with Auction chat

              • Major - Major loss of function.
              • Closed
              depends on

              Improvement - An improvement or enhancement to an existing feature or task. ICE-5664 Review use of Wrappers rather than directly subclassing interfaces.

              • Major - Major loss of function.
              • Closed
              is duplicated by

              Bug - A problem which impairs or prevents the functions of the product. ICE-5556 DOMResponseWriter requires should support all the same options for contentType and characterEncoding as jsf2.0

              • Major - Major loss of function.
              • Closed

                Activity

                Ascending order - Click to sort in descending order
                Deryk Sinotte created issue -
                Deryk Sinotte made changes -
                Field Original Value New Value
                Salesforce Case []
                Fix Version/s 2.0-Beta [ 10231 ]
                Hide
                Permalink
                Deryk Sinotte added a comment -

                Work to support the ResponseWriterWrapper should allow us to delegate the encoding detection.

                Show
                Deryk Sinotte added a comment - Work to support the ResponseWriterWrapper should allow us to delegate the encoding detection.
                Deryk Sinotte made changes -
                Link This issue depends on ICE-5664 [ ICE-5664 ]
                Deryk Sinotte made changes -
                Link This issue blocks ICE-5608 [ ICE-5608 ]
                Ken Fyten made changes -
                Link This issue is duplicated by ICE-5556 [ ICE-5556 ]
                Ken Fyten made changes -
                Assignee Deryk Sinotte [ deryk.sinotte ]
                Ken Fyten made changes -
                Salesforce Case []
                Affects [Compatibility/Configuration]
                Assignee Priority P1
                Deryk Sinotte made changes -
                Status Open [ 1 ] In Progress [ 3 ]
                Hide
                Permalink
                Deryk Sinotte added a comment -

                After the response writers to use wrappers, we are now able to use the supplied encoding where appropriate.

                I had successfully tested the use of Chinese characters on Mac OS X (Tomcat and Glassfish with Safari/Firefox/Chrome) using the latest from the trunk and could not reproduce the problem.

                I than switched over to Windows. After installing the East Asian character sets, I ran IE/Firefox/Chrome against Glassfish and still could not reproduce the issue. I asked Joanne to help and she was able to have everything working as well using here browsers as well as her test server. At this point, it appears that everything related to character encoding is working as required so I'm marking this as fixed as well as the more specific issue blocked by this.

                Show
                Deryk Sinotte added a comment - After the response writers to use wrappers, we are now able to use the supplied encoding where appropriate. I had successfully tested the use of Chinese characters on Mac OS X (Tomcat and Glassfish with Safari/Firefox/Chrome) using the latest from the trunk and could not reproduce the problem. I than switched over to Windows. After installing the East Asian character sets, I ran IE/Firefox/Chrome against Glassfish and still could not reproduce the issue. I asked Joanne to help and she was able to have everything working as well using here browsers as well as her test server. At this point, it appears that everything related to character encoding is working as required so I'm marking this as fixed as well as the more specific issue blocked by this.
                Deryk Sinotte made changes -
                Status In Progress [ 3 ] Resolved [ 5 ]
                Resolution Fixed [ 1 ]
                Ken Fyten made changes -
                Issue Type Bug [ 1 ] Improvement [ 4 ]
                Salesforce Case []
                Assignee Priority P1
                Ken Fyten made changes -
                Fix Version/s 2.0.0 [ 10230 ]
                Ken Fyten made changes -
                Status Resolved [ 5 ] Closed [ 6 ]

                  People

                  • Assignee:
                    Deryk Sinotte
                    Reporter:
                    Deryk Sinotte
                  • Votes:
                    0 Vote for this issue
                    Watchers:
                    0 Start watching this issue

                    Dates

                    • Created:
                      Updated:
                      Resolved: