[TAP] Add a configuration file property: 'coordinate_systems'. It lets list all allowed coordinate systems. By default, the list is empty, meaning that any is allowed.

[TAP] Change the default value for output and upload limits ; only negative value must mean 'no restriction' ; 0 must be a normal allowed value.

[TAP] Allow the TAP configuration file properties 'file_root_path' and 'metadata_file' be file pathes relative to WebContent.

[TAP] Add a property in the configuration file to set a custom TAPFactory (in replacement of ConfigurableTAPFactory.

[TAP] Add a 3rd possibility to set metadata in the TAP configuration file: give an extension of TAPMetadata having either an empty constructor or a constructor with a UWSFileManager, a TAPFactory and a TAPLog. & Rename function TAPConfiguration.isClassPath(String) into TAPConfiguration.isClassName(String).

[TAP] Add property to add/replace TAP resources & Add the tool function TAPConfiguration.newInstance(...).

[TAP] Add log management in the TAP configuration file. 2 additional properties have been added: min_log_level and log_rotation.

[TAP] Add missing formats (particularly all the different VOTable serializations) in the TAP configuration file

[TAP] Add a new database access method in the configuration file: get a Datasource from JNDI. & Better support of connection pooling (TAPFactory.countFreeConnections() has been removed ; when the creation of a database connection fails with an SQLException, it is considered that no connection are momentarily available...async jobs will be queued and all sync requests will be rejected).

[TAP] Add support for user identification in the configuration file. Besides, each time a property expected as an integer is not an integer, an exception is thrown.

[TAP] Add a parameter to limit the number of running asynchronous jobs in the configuration file: max_async_jobs.

[TAP] Add metadata support in the configuration file. Two methods to get metadata: 1/ Parse an XML file implementing the schema TableSet, and then re-build TAP_SCHEMA in the database, 2/ Get metadata from the database schema TAP_SCHEMA.

[TAP] Remove the availability fields from the configuration file. The Service will always start as available ; there is indeed no reason to start and leave it as unavailable.

+ Add the management of the Output Limit in TAPConfiguration
+ All the corresponding JUnit Tests
+ Replacing .properties test files for JUnit by a construction of Properties object
+ Update of the HTML documentation page and of the Full example file

TAP+TEST: First steps with the TAP configuration file management (Factory, ServiceConnection, but not yet Metadata) + their JUnit tests + documentation (the html file + configuration file examples)