Details

    • Type: Bug
    • Status: Closed
    • Resolution: Inactive
    • Affects Version/s: 6.2.0 CE GA1
    • Fix Version/s: None
    • Labels:
      None
    • Environment:
      Windows 7, Tomcat7, JRE7

      Description

      Calling method

      public static FileEntry addFileEntry(HttpPrincipal httpPrincipal, ..., File file, ServiceContext serviceContext)

      of DLAppServiceHttp only succeeds, when you supply a File parameter that is valid on the remote server and points to the very same file as on the originating system. Whenever the file parameter does not meet these unrealistic requirements the resulting DLFileEntry object gets nevertheless created, but with a size of 0 bytes.

      Why? I guess, that the File parameter gets successfully serialized and tunneled to the remote server, but accessing it there somehow results in an empty file.

      I suggest to completely remove this erroneous and misleading method from the API.

        Attachments

          Activity

            People

            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:
                Days since last comment:
                5 years, 34 weeks, 4 days ago

                Packages

                Version Package