Conversion Output Tree has a bug with InputConverters

[bergerkiller]

The output conversion tree is used to chain up converters in optimal routes from all possible input types towards a given output type. The problem is that Input Converters mess this up a little, because they use Object as input type. As a result, I see cases where it lazy-converts and Object to a String and then feeds that into the input converter.

Input converters shouldn't at all be stored in the conversion tree. They should instead be queried for every new input type to populate new converters (getConverter()).

[bergerkiller]

Input converters need to provide information about what input types are supported. Without this there is no way to link up input converters together with normal converters to create a valid chain. This also ends the problem of having more than one input converter creating the same type; right now this fails due to the Output List.

Suggested is storing a List of supported input types which can be queried. The default 'input' field of the converter should default to Object at all times. Add a function called 'getInputs()' to query the real generic input types, and a protected 'addInput' member to register new types.