- Apr 23, 2018
-
-
gmantele authored
forwarding toward a JSP file in the WebContent directory. The name of the attribute is merely `tap`.
-
- Apr 09, 2018
-
-
gmantele authored
While waiting for a clean ADQL-2.1 implementation, the BOOLEAN datatype will be still considered as SMALLINT. But at least, the TableSetParser (used in the ADQL-Library Online Validator) won't reject tables.xml with a BOOLEAN datatype.
-
- Mar 21, 2018
-
-
gmantele authored
-
gmantele authored
-
gmantele authored
Merge pull request #68 from olebole/fix-java9: Test: Compare only the first 8 digits in string comparison
-
Ole Streicher authored
In TestPgSphereTranslator, two strings are compared containing (double) floating point numbers. These numbers are slightly different with different Java versions. To overcome this, only the first eight fractional digits are compared.
- Mar 07, 2018
-
-
gmantele authored
The end of the description of a UDF was not detected when this UDF was followed by another UDF definition. This was due to an incorrect double quote escape in the regular expression of a UDF's definition.
-
- Mar 02, 2018
-
-
gmantele authored
-
gmantele authored
The UWS-1.x standard defines the quote as an ISO-8601 date. UWS-Lib stores it as a number of seconds (i.e. estimated job duration). This fix ensures that this integer/long quote value is returned as a date. Note: The backup and restoration processes are not affected by this change. The backup file format is still the same: a quote stored as a long value.
-
- Feb 26, 2018
-
-
gmantele authored
-
gmantele authored
-
gmantele authored
It is possible to choose how the blocking mechanism should behave (e.g. what the max. waiting period, how many requests can be blocked in the same time, what happen when the blocking times out, ...). Indeed, the policy to apply must actually be an extension of the interface BlockingPolicy. Already two implementations are provided in the library (LimitedBlockingPolicy and UserLimitedBlockingPolicy), but a custom policy can perfectly be created and apply to a UWS service. By default, no policy is set. In such case, the service will block the time specified by the user, which may be -1 (i.e. wait indefinitely). A BlockingPolicy can help controlling the waiting/blocking process and protect the resources of the server.
-
gmantele authored
- PHASE: list only jobs in the specified PHASE. If this parameter is repeated jobs matching any of the specified phases will be returned. - AFTER: list jobs created after the specified ISO-8601 date (included). If this parameter is repeated, only the most recent date is retained. - LAST: list the N-th most recently created jobs, ordered by descending creation time These filter parameters are additive: their constraints are joint as with an AND operator (except for PHASE parameters ; see above). If no filter is specified, all jobs EXCEPT the ARCHIVED ones are listed. The only way to list ARCHIVED jobs is to use PHASE=ARCHIVED (with or without other filter parameters). The filtering API has been made in a generic manner so that it is easily possible to create and add new filters. See the interface JobFilter and the class JobListRefined for more details.
-
gmantele authored
and ALWAYS_ARCHIVE. When archiving a job, its former phase is stored in jobInfo under the name 'oldPhase' if no jobInfo is already set. Archiving a job means that all input files and results are destroyed ; the error summary and jobInfo (even if it is a file) are kept. Each archive operation ends with a log message ; in ERROR if failed or in INFO if successful. This commit also includes the following things: - reformat on 80 characters width the Javadoc of all modified classes - fix a bug with the phase transitions: since it is not possible any more to go from PENDING to EXECUTING directly, UWSJob.start(...) must first ensure to be on QUEUED phase. This bug has also been fixed in TAPJob. Similarly, before going into ARCHIVED phase the job must be set into ABORTED phase if not already in a final phase.
-
gmantele authored
A JUnit test case has been added in order to check that all possible phase transitions are respecting the UWS-1.1 standard. However, there is anyway a bit more freedom for some of them: - it is possible to go to and come from UNKNOWN at any time, whatever is the source or target phase. - it is possible to go to ERROR or ABORTED from the phases HELD and SUSPENDED. This fact was not specified in the State Machine figure of the UWS standard but the following sentence at section "2.1.3 Execution Phase" (page 7) should allow that: "At any time before the COMPLETED phase a job may either be ABORTED or may suffer an ERROR." - the UWS-1.1 document has an inconsistency about the HELD phase. At section "2.1.3 Execution Phase" (page 7), the following sentence implies that it is only possible to go to HELD from PENDING (because it would not be possible to queue the job). And so, when PHASE=RUN is sent by the UWS client, if now possible, the job should go in phase QUEUED. However the State Machine figure suggests that it is possible to go to HELD only from EXECUTING and that a PHASE=RUN would make the job go back to EXECUTING (if now possible). Because of this inconsistency, the UWSLibrary made possible the following transitions: PENDING/EXECUTING->HELD->QUEUED/EXECUTING. (note: a figure illustrating the phase transitions supported by the UWSLibrary-4.3 has been created in the directory `img` of the UWS-Tutorial website under the file name `state_machine.png`...which of course will be visible only when uwslib-4.3 will be released) Besides, this commit also include almost a full rewriting of the Javadoc of JobPhase and ExecutionPhase. The Javadoc of UWSJob has just been reformated so that comments do not exceed 80 (+2) characters. This reformating aims to improve the human reading of the Javadoc while looking at the source files ; however this should not affect much the HTML version of the Javadoc.
-
gmantele authored
This property is displayed in the XML and JSON serialization of a job item. It is also backuped and restored from a UWS backup file. /!\ WARNING: Small modification of the API! Since creationTime must be set by the UWS service at creation of a job, this date must also be imported at backup restoration. Hence the modification of the interface uws.service.UWSFactory and its implementations (particularly tap.AbstractTAPFactory). Similarly the class uws.job.UWSJob and tap.job.TAPJob have underwent exactly the same modification in one of their constructors. This commit also adds the new optional jobRef items: creationTime, runID and ownerID in the XML and JSON serializations.
-
gmantele authored
<job>. This commit also: - set the version of the UWS protocol to 1.1 (cf UWS.VERSION) - add a static constant for the standardID (cf UWS.STANDARD_ID) - add a xlink:type and xlink:href for jobListRef in the uws XML - set the @version Javadoc attribute of all modified classes to 4.3 (scheduled version of the UWSLibrary supporting UWS-1.1)
-
gmantele authored
serialization of all results if such information are available. This commit also fix few comments about the result's XML serialization. The processing of xlink:type of a result reference is made similar as the one of jobRef.
-
gmantele authored
Although the Java code allowed the specification of a description of a User Defined Function, it was not possible to set one in the UDFs listed in the configuration file.
-
- Feb 22, 2018
-
-
gmantele authored
-
- Feb 08, 2018
-
- Jan 31, 2018
- Jan 12, 2018
-
-
gmantele authored
Now, JDBCConnection is fully capable to test the existence of schemas, tables and columns of a MySQL database. Thanks to @zonia3000 for solving this issue.
-
gmantele authored
Merge pull request #59 from zonia3000/master
-
gmantele authored
* The parsing did not allow unsigned numerics and SQL SET functions as specified in the ADQL 2.0 grammar * It was even forbidden to put a column whose the type is not String. * The translation of a concatenation expression was always prefixed by the ADQLList's name: CONCAT_STR. Of course, no database likes that... Regarding this last point, this commit fixes the GitHub issue #54
-
- Jan 11, 2018
- Jan 08, 2018
-
-
gmantele authored
This commit fixes the Github issue #58
-
- Nov 30, 2017
-
-
gmantele authored
if the alias is not delimited in ADQL. This commit fixes the GitHub issue #56
-
gmantele authored
are translated: the table part (if a reference to an aliased table) should be as declared in the DBTable (especially now that we have DBTableAlias to deal nicely with table aliases).
-
gmantele authored
this table is declared with an alias. Instead, the table alias must be used. Note: This problem occurred only when ADQLParser was used with a DBChecker. This commit fixes the GitHub issue #53
-
- Nov 16, 2017
-
-
gmantele authored
The order of its children was incorrect according to the XSD schema: the 'fkColumn' must be written before 'description' and 'utype'.
-
- Nov 10, 2017
-
-
gmantele authored
A delimited identifier is any sequence of characters between a pair of double quotes. For instance: "123 I am a delimited identifier!". It is of course possible to have double quotes inside this kind of identifier, but they have to be doubled in order to not be mistaken with the end of the identifier. For instance: "Cool ""identifier""". However, this escape option was not taken into account by the ADQL library, though the same mechanism was already in place for string contants.
-
- Sep 27, 2017
-
-
gmantele authored
This commit also includes the 2 following points: - for (really really tiny) optimisation purpose, replace String by a char when there is only one character to append to a StringBuffer - add a bit more details about Result.type in the Javadoc (it should be a xlink:type and not a random custom type)
-
gmantele authored
Until now, it was possible to destroy the job by posting ACTION=DELETE with a URL like below: {root-uws}/{job-list}/{job-id}/foo/bar That is completely wrong. The correct URL for this action must always be: {root-uws}/{job-list}/{job-id} This commit fixes this error in UWSServlet and UWSService.
-
gmantele authored
The configuration of the DestructionTimeController was never effective in the UWSServlet with a configuration file: the wrong instance was set.
-
gmantele authored
synchronized although the collection of observers is synchronized (Vector) ; using an Iterator ensures the synchronization and avoids concurrency problems.
-
gmantele authored
- uws.service.UWS.VERSION (static final) - tap.resource.TAP.VERSION (static final) Dealing with several protocol versions in the same time is quite difficult and may significantly alter the libraries API in an unstable way. That's why, for the TAP and UWS libraries, only one version is implemented (i.e. the last one). To use a older version of the protocol, one must use an older version of the corresponding library. About the versioning of the ADQL standard, there is no need to set any version number somewhere because a different ADQL version implies a different grammar. It means that a different parser is required for each ADQL version. For the moment, there is only one version, so no need to change anything to the ADQL library about ADQL version. Later, ADQLParser should become an interface and a factory will have to be used in order to get the parser corresponding to the desired ADQL version.
-