Current behavior:
All the SQL activities either don't support Insert or are specific to a usecase

Expected behavior:
to be able to insert to a sql database in an activity

What is the motivation / use case for changing the behavior?
many workflows/pipelines require logging to a database

Additional information you deem important (e.g. I need this tomorrow):

The kamel init Foo.java command generates source code that has an ASF license header.

But since this is for end users and they may use other licenses or none at all, then we should generally not include a header out of the box. This also makes the code smaller and leaner and quicker to overview and understand.

This applies also to the other languages it can generate for like groovy, kotlin

ask {
    const marta = { firstName: 'Marta' }
    marta:at('firstName3')
}

returns null (empty) but an error was expected (playground with AskVM v. 1.2.0)