grgrzybek commented on PR #10000: URL: https://github.com/apache/camel/pull/10000#issuecomment-1537418064
Sure, as I said - naming is work in progress. Package scanning is a must and we could simply: * register beans with default ctor * register beans with `@Named` and `@Inject` constructors Yaml dsl code is a bit weird for me (at this stage of grasping Camel changes), but definitely there must be one mechanism underneath. `<camel-app>` and `<beans>` are kind of aliases, but for now the first one looks more natural (as there are no `<bean>` element to justify `<beans>` :D). Another thought - if Spring's top-level `<beans>` would be supported, it should be able to use `<camelContext>` inside and it's more a work related to CAMEL-19041. Anyway - the hardest part for me is done (which was to actually write some initial code). I start slowly, but then it's easier for me ;) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
