Announcement

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

    Bug with binary functionallity

    We moved from using SGWT 2.3 22-12-10 nightly build to the latest 2.4 nightly build.

    From that changed we get "Closed connection" on any binary function we use.
    (when re-building with 2.3 it works)

    We use ojdbc5, windows xp, and Oracle9 DB.

    Is it a known bug?

    #2
    Not a known bug, and samples that use binary are working. Trying putting together a test case.

    Comment


      #3
      sorry the problem is not with binaries but with clobs.

      Comment


        #4
        it reminds us of this fix: http://forums.smartclient.com/showthread.php?t=12275&page=3

        and to be more clear, the problem is both with BLOBs and CLOBs.
        (we can`t download BLOBs and view CLOBs)
        and it is working when we recomiple with 2.3

        Comment


          #5
          we tried uploading to a server with JNDI (using 2.4) and it made the CLOBs functionality work, but BLOBs are still not working (on server the all blobs seem to be null..)

          thanks!

          Comment


            #6
            Please post all the required information (the text you need to delete in order to post).

            Comment


              #7
              we're using smartgwtee

              our developing environment is completely detached from the internet, that is why we usually don't add logs/code etc.
              I've copied some of the stack traces manually this time.

              let's seperate the two problems:

              1. The Clob problem: only on hosted mode
              when we try to fetch from a DS which has clobs in it we receive the following exception on the server side:
              java.io.IOException - ConnectionClosed
              .
              .
              oracle.jdbc.driver.OracleClobReader.read(line 136)
              .
              .
              com.isomorfic.util.IOUtil.copyCharacterStreams(183)
              com.isomorfic.util.IOUtil.copyCharacterStreams(127)

              when we deploy it on our weblogic server it works fine, it also works with 2.3
              again we already encountered this problem: http://forums.smartclient.com/showthread.php?t=12275&page=3

              2. The Blob problem: happens on both hosted and deployment
              All the Blobs seems to be null at client side, and when I try to upload a binary file I get a not very informative Exception on the client side

              RPCManager:Error performing:'....._update' error:FAILURE
              .
              .
              sun.reflect.NativeConstructorAccessorImpl.newInstance0()

              we're using ojdbc5.jar if it makes any difference.

              This also works on smartgwtee 2.3

              I hope It's clearer now...

              Comment


                #8
                anyone?

                we can`t move to 2.4 without it :\

                Comment


                  #9
                  isomorphic?
                  if you need more details than that please let us know.

                  Comment


                    #10
                    Is this with a "sql" DataSource or some other type? And what are the types of the CLOB and BLOB fields in your.ds.xml file?

                    Comment


                      #11
                      1. yes an 'SQL' datasource
                      2. CLOB- text of a length of 10000
                      BLOB - binary

                      Comment


                        #12
                        anything new?


                        thanks!!

                        Comment


                          #13
                          Yes, this was a bug which has now been fixed.

                          Comment


                            #14
                            we tried with the latest nightly build.

                            it fixed the CLOB issue,
                            but BINARY fields are still seem as null in the client.

                            Comment


                              #15
                              OK, we figured out what was wrong.

                              Record.getAttribute() for binary fields started returning null for some reason even if the binary field wasn't null.
                              We can check the *_filesize or *_filename attributes to see if the field is null.

                              Comment

                              Working...
                              X