Hi We have some less known features in camel-core https://camel.apache.org/manual/validator.html https://camel.apache.org/manual/transformer.html
That can be used to associate route(s) with a data type contract, and have the route automatically validate if the input/output is as expected to this contract. You can also associate routes with automatic transformation with data-formats. However all of these are not really in use, and it has had limited innovation since its addition. They are part of the model but to set up the validator/transformers then this is not fully implemented in all DSLs and make them harder to use outside Java or the legacy XML for blueprint/spring. Today the high level building blocks are Kamelets where you can/should specify the data shape of the kamelet as input/output etc. In light of this I think we should deprecate the data contract we have today and focus on data contracts on Kamelets, and re-architect a more modern cloud native perspective for this. A search on the user mailing list, then, I could only find a post from 2017 from a CXF user that declared Camel route with an inputType(MyClassHere.class) to setup a route data type. -- Claus Ibsen ----------------- http://davsclaus.com @davsclaus Camel in Action 2: https://www.manning.com/ibsen2
