Adjust schemas to match jms and evaluator

[wehrler]

No description provided.

[FedericoNegri]

@wehrler I've pushed a commit to enhance the script that auto-generates the resources code so to include more dict type info.

Here as well would be good to cover your changes with tests (mostly to cover correct serialization and deserialization, and verify that the schema rejects unsupported types already at client level).

[wehrler]

@wehrler I've pushed a commit to enhance the script that auto-generates the resources code so to include more dict type info.

Here as well would be good to cover your changes with tests (mostly to cover correct serialization and deserialization, and verify that the schema rejects unsupported types already at client level).

Do we want tests targeting the schema adjustments in general? (e.g. The tests for JMS target the new any_value field that I created. I chose this instead of the fields where it is applied due to the coupling of TaskDefintionSchema to an actual request session.)

[wehrler]

@wehrler I've pushed a commit to enhance the script that auto-generates the resources code so to include more dict type info.
Here as well would be good to cover your changes with tests (mostly to cover correct serialization and deserialization, and verify that the schema rejects unsupported types already at client level).

Do we want tests targeting the schema adjustments in general? (e.g. The tests for JMS target the new any_value field that I created. I chose this instead of the fields where it is applied due to the coupling of TaskDefintionSchema to an actual request session.)

@FedericoNegri - *see latest. (I added a test for de/serialization of task definitions).