Skip to content
  1. Jul 08, 2015
  2. Jun 18, 2015
  3. Jun 16, 2015
  4. Jun 03, 2015
  5. Jun 02, 2015
  6. May 21, 2015
  7. May 19, 2015
    • Mark Taylor's avatar
      fix ADQL build file to permit cross-compilation · 7a618199
      Mark Taylor authored
      You can now set the adql.bootclasspath system property to use
      an alternative bootclasspath, for instance that for a different
      JRE than that used by the compiler.
      
      For instance, this cross-compiles to java 1.5:
      
         ant -Dant.build.javac.target=1.5
             -Dadql.bootclasspath=/usr/java/jdk1.5.0_22/jre/lib/rt.jar
             -f buildADQL.xml
             buildLib
      
      Note the java used by ant has to be at least java 6 because of the
      @Override source constructs on methods inherited from interfaces
      (only methods from abstract or non-abstract classes can be annotated
      with @Override in java 5).
      7a618199
    • Mark Taylor's avatar
      replace references to since-J2SE6 methods in ADQL lib · 6f8ff70a
      Mark Taylor authored
      Replace uses of String.isEmpty and Arrays.copyOf methods
      (both introduced in java 6) with equivalent code that makes
      use of only methods available in the java 5 runtime.
      This allows the ADQL library, if cross-compiled for java 5,
      to run without errors on a java 5 runtime.
      6f8ff70a
  8. May 06, 2015
  9. May 04, 2015
  10. Apr 22, 2015
  11. Apr 13, 2015
  12. Apr 09, 2015
  13. Apr 08, 2015
  14. Apr 02, 2015
    • gmantele's avatar
    • gmantele's avatar
      [UWS,TAP] Errors and log management improvements. Particularly, now TAP and... · 998d11f5
      gmantele authored
      [UWS,TAP] Errors and log management improvements. Particularly, now TAP and UWS are able to manage correctly HTTP request abortions (i.e. when the user stop the request before the response has been fully sent, or when there is a connection problem or a time-out). Such abortions are considered by UWS and TAP merely as job abortion/cancel. No error is logged any more. In addition of this correction, log entries concerning the execution of a TAP sync/async job have been modified so that having more coherents messages. And stack traces of exception that occurred when executing a job (sync or async, tap or uws) are displayed just once: at the JOB END log entry, and not by the HTTP RESPONSE_SENT entry. And finally, output flush and interruption detection are made more often when writing a query result (the flush is particularly important when combining with fetch-size > 0 in synchronous mode....the sync response is then a streaming output).
      998d11f5
  15. Mar 26, 2015
  16. Mar 13, 2015
  17. Mar 11, 2015
  18. Mar 10, 2015