Skip to content
Snippets Groups Projects
  1. Nov 13, 2014
    • gmantele's avatar
      [UWS,TAP] Review the standard parameters checking. Particularly, because... · 2a1e5786
      gmantele authored
      [UWS,TAP] Review the standard parameters checking. Particularly, because before, the default value was never used while no value was specified by the user.
      2a1e5786
    • gmantele's avatar
      [UWS] Cancel last commit. The UWSException was thrown intentionnaly: if an... · 425d77e9
      gmantele authored
      [UWS] Cancel last commit. The UWSException was thrown intentionnaly: if an error occurs while just creating the thread, this error should not impact the job ; it is an internal server error, not an error due to the job execution or of a wrong parameter. This error MUST be thrown AND the job MUST stay PENDING (so that it can be restarted later when the server bug will be fixed). Job parameters checks MUST be done either in the job execution (JobThread.jobWork()) or at the job creation (using an InputParamController).
      425d77e9
  2. Nov 12, 2014
  3. Oct 22, 2014
  4. Oct 14, 2014
  5. Oct 01, 2014
  6. Sep 25, 2014
  7. Sep 23, 2014
    • gmantele's avatar
      [TAP,UWS] Fix a problem with the format of the error details returned by the... · 9aa13889
      gmantele authored
      [TAP,UWS] Fix a problem with the format of the error details returned by the parameter .../error/details. In TAP a VOTable document is expected, but a text/plain description was returned (default behavior in the UWS lib.). Now, a ServiceErrorWriter is used to format the error details correctly.
      9aa13889
    • gmantele's avatar
      [TAP,UWS] Small log corrections (for Thread logs, display the thread name... · b40638f4
      gmantele authored
      [TAP,UWS] Small log corrections (for Thread logs, display the thread name rather than the ID ; the job id was forgotten in the log of CHANGE_PHASE ; build a UWSException with the given throwable message as message ; in log TAP for the event EXECUTING, the memory address of the ADQLQuery object was displayed rather than of the ADQL query expression ; display the stack trace of the SQLException.getNextException() when calling logDB)
      b40638f4
  8. Sep 17, 2014
  9. Aug 20, 2014
  10. May 28, 2014
  11. Apr 10, 2014
  12. Apr 03, 2014
Loading