[UWS,TAP] 3 MAJOR DEPENDENT FIX: improve significantly the parameters extraction from HTTP request in UWS (1) AND move the file-upload ability into the UWS library (2) AND the modification of parameters in UWS is now conform with the standard (3). (1) Only application/x-form-urlencoded content-type was supported. However a UWS must accept a request body containing only an XML document as a single byReference parameter. It is now done when the content-type is not known. (2) Besides multipart/form-data is now fully supported in UWS and so is still possible in TAP. (3) In the UWS standard, parameters can not be added after creation: they can just be modified. This rule is now respected in the UWS library.

[TAP] Deal with the DB type 'BOOLEAN' while uploading boolean values in the database => convert the boolean in a short value (1 or 0).

[ADQL] Keep the same order of columns as they are added inside the DBTable => use a LinkedHashMap rather than a HashMap

[TAP] Make TAP and UWSService use the same ServiceErrorWriter AND make DefaultTAPErrorWriter use the same VOTableFormat as the one declared as OutputFormat in the ServiceConnection.

[TAP] Fix a grave error: synchronous jobs were stopped much before the specified execution duration ; the library was waiting N milliseconds, where N is the TAP execution duration always expressed in seconds.

[UWS,TAP] Review the standard parameters checking. Particularly, because before, the default value was never used while no value was specified by the user.

[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).

[ADQL,TAP] Add geometry format in output and correct upload of STC-S regions. Geometrical type conversion from and into a DB type is now required in all JDBCTranslator. This allows formatting of geometrical column value coming from the database, but also the translation of STC-S expressions provided in uploaded table into geometrical column values.

[ADQL] Support the special escaping syntax for string literals in Postgres (strings to escape must be prefixed by a E before the starting ').

[TAP] Do not write optional XML attributes in the /tables when their value is NULL or an empty string.

[ADQL,TAP] Add STC-S and UDFs support in the ADQL parser. Now, it is possible to provide a list of allowed UDFs, regions and coordinate systems. The ServiceConnection of TAP is now able to provide these lists and to propagate them to the ADQLExecutor. UDFs and allowed regions are now listed automatically in the /capabilities resource of TAP. The type 'geometry' is now fully supported in ADQL. That's why the new function 'isGeometry()' has been added to all ADQLOperand extensions. Now the DBChecker is also able to check roughly types of columns and UDFs (unknown when parsing syntactically a query). The syntax of STC-S regions (expressed in the REGION function) are now checked by DBChecker. However, for the moment, geometries are not serialized in STC-S in the output....but it should be possible in some way in the next commit(s).

[UWS] End of 'Fix synchronization bug while generating the default Job ID' (commit e6a9d52f)

[UWS] Correct the way the URL interpreter is used: at initilization with a HttpServletRequest, the full URL until the base URI should be saved + In UWSService, the used URL interpreter was a class attribute, which is a bad thing (this object is shared by several threads).

[TAP] Log format reports and end of ADQLExecutor execution, add an OVERFLOW notification for the text/plain output and check by default that the given service connection is not null in constructor.

Conflicts:
	src/tap/formatter/VOTableFormat.java

[TAP] Adapt the MIME type of VOTable output in function of the chosen data part serialization AND let setting the VOTable MIME type after creation (useful only when no known serialization is chosen).

[TAP] Adapt the MIME type of VOTable output in function of the chosen data part serialization AND let setting the VOTable MIME type after creation (useful only when no known serialization is chosen).

[UWS] Make XML representation of jobs and joblists valid (with their XML schema), and particularly the nodes jobs, job and the error type (which should be written in lower-case).

[UWS,TAP] Fix timestamp format. Now, each returned date will expressed in UTC and using the ISO8601 format. Any given date is also expected in UTC (or with a time zone offset) and in ISO8601Format. These rules apply also for uploaded tables and for timestamp columns in a query result.

[ADQL] Remove useless Javadoc (no custom javadoc for files automatically generated from the JavaCC grammar)

[TAP,UWS] Make valid VOTable results and errors. Some error messages about expected TAP request parameters have been changed.

[TAP] Make valid the /tables document (using a XSD schema correct copy of GAVO for VOSITables ; the IVOA one is incorrect: the attribute targetNamespace is not ...VOSITables...)

[TAP] Fix bug in upload (uploaded tables were given twice to the db checker) & Allow customization of the DB upload schema in the tap factory

[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.

[TAP] Fix MAXREC bug (maxrec was ignored if = 0) & Replace the MIME type for VOTable output from 'text/xml' to 'application/xml'