Improve mdc.adoc

[abedurftig]

I was trying to get this running in my Spring Boot application. I noticed that the documentation could be improved.

• update the usage; auto-configuration only works of the camel-mdc-starter is added
• otherwise service must be created and added
• camel.mdc properties names didn't match implementation

[davsclaus]

For Spring Boot you should always use the -starter - that is for all of the camel components.

[squakez]

We don't generally explain in the components how to deal when adopting springboot or main (or quarkus). It is kind of implicity that, in order to use a component, then you have to add the component dependency or starter (or quarkus extension).

As for the property names, yes, they had to be fixed, thanks. However, I'd keep the example explanation in order to show the user how to use wildcards when they want to include any pattern for a property or header.

IMO, the only change we should add are the property names changes.

[abedurftig]

Thanks for your feedback. I was not able to get it working right away. The fact that there might be a starter occurred too late, that's why I updated the docs. But if this is a convention, then maybe redundant.

Are these conventions documented somewhere?

Should I revert everything but the property names?

[github-actions]

🌟 Thank you for your contribution to the Apache Camel project! 🌟
🤖 CI automation will test this PR automatically.

🐫 Apache Camel Committers, please review the following items:

• First-time contributors require MANUAL approval for the GitHub Actions to run
• You can use the command /component-test (camel-)component-name1 (camel-)component-name2.. to request a test from the test bot although they are normally detected and executed by CI.
• You can label PRs using skip-tests and test-dependents to fine-tune the checks executed by this PR.
• Build and test logs are available in the summary page. Only Apache Camel committers have access to the summary.

⚠️ Be careful when sharing logs. Review their contents before sharing them publicly.

[github-actions]

🧪 CI tested the following changed modules:

• components/camel-mdc

All tested modules (8 modules)

• Camel :: JBang :: MCP
• Camel :: JBang :: Plugin :: Route Parser
• Camel :: JBang :: Plugin :: TUI
• Camel :: JBang :: Plugin :: Validate
• Camel :: Launcher :: Container
• Camel :: MDC
• Camel :: YAML DSL :: Validator
• Camel :: YAML DSL :: Validator Maven Plugin

---

⚙️ View full build and test results

[davsclaus]

Thanks for your feedback. I was not able to get it working right away. The fact that there might be a starter occurred too late, that's why I updated the docs. But if this is a convention, then maybe redundant.

Are these conventions documented somewhere?

in the camel spring boot docs
https://camel.apache.org/camel-spring-boot/4.18.x/index.html

Should I revert everything but the property names?

yes thanks as suggested by @squakez

[abedurftig]

Alright. There were some changes on main on the exact lines of code, so I rebased and cleaned up. So, the changes are really only the property names.

in the camel spring boot docs

Thanks for sharing.