Announcement

Collapse
No announcement yet.
X
  • Filter
  • Time
Clear All
new posts

    #16
    Yes, I am absolutely sure.

    Today I tried again:

    I compiled first with 5.0p power 27.01.15, and the characters were *not* shown correctly.

    I immediately changed to 4.1p power 09.11.14 and the characters were shown correctly.

    This is the only thing I changed.

    Comment


      #17
      We still can't reproduce this, it looks like the data is corrupted *after* SmartGWT is done processing it. So we need some more information:

      1. First of all, please add encoding=UTF-8 parameter to your log4j config, see below XML example of appender with this parameter. In this case UTF-8 will be used in log and we'll see if fileName value will reach Smartclient server side unchanged. Please make sure you do this to correct appender (you might use different set of appenders), or you may apply this to all of them.

      Code:
      <appender name="STDOUT" class="org.apache.log4j.ConsoleAppender">
      [b]    <param name="encoding" value="UTF-8"/>[/b]
          <layout class="org.apache.log4j.PatternLayout">
          <param name="ConversionPattern" value="=== %d [%.4t] %-5p %c{1} - %m%n"/>
          </layout>		
      </appender>
      2. Do actual logging - you should print fileName value to log without any conversion/decoding right from you DMI method. In addition please enable DEBUG log level for RPCManager, like shown below. This will enable logging of request payload, which will include values sent to server.
      Code:
      <category name="com.isomorphic.rpc.RPCManager">
          <priority value="DEBUG" />
      </category>
      3. Please show us request and response headers of this http POST (using tools like Firebug in FF). Please make sure to send headers for this exact call you are getting wrong fileName from.

      4. Please repeat all 3 steps above for 4.1 version where things work fine and 5.0 where they don't.

      Thank you for your patience.

      Comment


        #18
        This is for the 5.0 version:

        1. Ok, done
        2.
        Filename logs:
        Code:
        LOG.info("I will now print the filename received: ");
        		LOG.info(values.get("filename"));
        actual log:
        Sent you per Email, since too large to post here.

        3. Request headers:
        Code:
        POST /kids-dev/V010305SNAPSHOT/sc/IDACall?isc_rpc=1&isc_v=v10.0p_2015-02-27&isc_tnum=0 HTTP/1.1
        Host: localhost:8081
        Connection: keep-alive
        Content-Length: 1012
        Cache-Control: max-age=0
        Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
        Origin: http://localhost:8081
        User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
        Content-Type: application/x-www-form-urlencoded
        Referer: http://localhost:8081/kids-dev/
        Accept-Encoding: gzip, deflate
        Accept-Language: de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4
        Cookie: JSESSIONID=3B631B3FF41148C09266AFEF73CD5431; GWT_LOCALE=de; human.version=1.3.6%20pre-release%20development%20version%2020150309-2230; isc_cState=ready; GLog=%7B%0D%20%20%20%20trackRPC%3Afalse%0D%7D
        isc_rpc:1
        isc_v:v10.0p_2015-02-27
        _transaction:<transaction xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xsi:type="xsd:Object"><transactionNum xsi:type="xsd:long">0</transactionNum><operations xsi:type="xsd:List"><elem xsi:type="xsd:Object"><values xsi:type="xsd:Object"><filename>äöü</filename></values><operationConfig xsi:type="xsd:Object"><dataSource>simpleTable</dataSource><repo xsi:nil="true"/><operationType>custom</operationType><textMatchStyle>exact</textMatchStyle></operationConfig><appID>builtinApplication</appID><operation>getTextFile</operation><oldValues xsi:type="xsd:Object"><filename>äöü</filename></oldValues></elem></operations><jscallback>iframe</jscallback></transaction>
        protocolVersion:1.0
        __iframeTarget__:isc_HiddenFrame_0
        Response headers:
        Code:
        Content-Disposition:attachment; filename="%C3%A4%C3%B6%C3%BC.txt"; filename*=UTF-8''%C3%83%C2%A4%C3%83%C2%B6%C3%83%C2%BC.txt
        Content-Length:0
        Content-Type:text/plain;charset=UTF-8
        Date:Mon, 09 Mar 2015 22:14:26 GMT
        Server:Apache-Coyote/1.1
        X-Included-Test:true
        X-Included-Test2:true
        Last edited by edulid; 10 Mar 2015, 01:41.

        Comment


          #19
          This is for the 4.1p version:

          1. Ok
          2. Filename logs:
          Code:
          LOG.info("I will now print the filename received: ");
          		LOG.info(values.get("filename"));
          actual log:
          Sent you per Email, since too large to post here.

          3 Request headers:
          Code:
          Accept:text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8
          Accept-Encoding:gzip, deflate
          Accept-Language:de-DE,de;q=0.8,en-US;q=0.6,en;q=0.4
          Cache-Control:max-age=0
          Connection:keep-alive
          Content-Length:976
          Content-Type:application/x-www-form-urlencoded
          Cookie:JSESSIONID=360D7A94CC6B2888E70DAF1AAA04CC88; isc_cState=ready
          Host:localhost:8081
          Origin:http://localhost:8081
          Referer:http://localhost:8081/kids-dev/
          User-Agent:Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/40.0.2214.115 Safari/537.36
          isc_rpc:1
          isc_v:v9.1p_2014-11-09
          isc_tnum:0
          _transaction:<transaction xmlns:xsi="http://www.w3.org/2000/10/XMLSchema-instance" xsi:type="xsd:Object"><transactionNum xsi:type="xsd:long">0</transactionNum><operations xsi:type="xsd:List"><elem xsi:type="xsd:Object"><values xsi:type="xsd:Object"><filename>äöü</filename></values><operationConfig xsi:type="xsd:Object"><dataSource>simpleTable</dataSource><operationType>custom</operationType><textMatchStyle>exact</textMatchStyle></operationConfig><appID>builtinApplication</appID><operation>getTextFile</operation><oldValues xsi:type="xsd:Object"><filename>äöü</filename></oldValues></elem></operations><jscallback>iframe</jscallback></transaction>
          protocolVersion:1.0
          __iframeTarget__:isc_HiddenFrame_0
          Response headers:
          Code:
          Content-Disposition:attachment; filename="%E4%F6%FC.txt"; filename*=UTF-8''%C3%A4%C3%B6%C3%BC.txt
          Content-Length:0
          Content-Type:text/plain;charset=UTF-8
          Date:Mon, 09 Mar 2015 22:28:37 GMT
          Server:Apache-Coyote/1.1
          X-Included-Test:true
          X-Included-Test2:true

          Comment


            #20
            Thank you for all this additional information, especially for your test cases wars. We deployed your both your wars and 4.1 works OK, but 5.0 indeed is not working. Finally, this is reproduced and can be fixed. We'll keep you informed.

            Comment


              #21
              Any updates on this issue?

              Comment


                #22
                This is still being looked at. It's proving very tricky to debug - we are unable to reproduce it outside of your wars so are trying to pin down what is special in your web-app that causes the problem to manifest.

                We'll follow up when we have something and rest assured we are working on it!

                Regards
                Isomorphic Software

                Comment


                  #23
                  Ok, so this was in fact a regression. Apologies. This problem actually affects both 5.0 and 5.1. It has now been fixed and will be in the March 24th build.

                  Thanks again for the standalone test case - that really helped.

                  Comment


                    #24
                    Why actually not in the 23th build?

                    I have checked the builds today: 4.1p 24.03 is released, but 5.0p not, only 23.03.

                    Comment


                      #25
                      The 5.0 build process hasn't finished yet.

                      Comment


                        #26
                        The bug is fixed in the 24.03, thanks.

                        Comment


                          #27
                          Great - thanks for confirming.

                          Comment

                          Working...
                          X