Build DataSource-Configuration new from scratch

Description

Initial situation:
--------------------------------------------------------------
When using the DataSource-Configuration-Framework you have to use
the new overload of the putParameterValues-Method and must call a
init-Method.

It´s only possible to use a XML or a properties-Configuration.

--------------------------------------------------------------

Actual behavior:
--------------------------------------------------------------
It feels ugly when using the api and feels not correct to do so.
The value of the DataSource-Designer
is passed to the Method but the value isn´t used and is overriden
with values from a Configuration-File.

In my and some colleagues opinion the API is designed very poorly and
should be built new from scratch.

------------------------------------------------------------- Suggestions for a new implementation
------------------------------------------------------------- We should use an interface e.g. <<ExternalConfiguration>>
and make different implementations for where the config is from.
This could be e.g. a .properties-File or a XML-File or the implementation
could get the values from a webserver.
With the Interface it´s also very easy to extend the API with new
ways of configuration.

The IDE-Integration could look like this:

There´s a checkBox in the DataSource designer to decide if the
values typed in the Fields should be used, or one can choose in a
ComboBox which ExternalConfiguration-Implementation to use.

Environment

None

Assignee

FH

Reporter

Holger Lober

Labels

None

Epic/Theme

None

Affects versions

Priority

Major