Hello Christofer, Thanks for reaching out and for your ongoing support of Karavan.
To answer your questions about customized component editors: 1. Current Architecture: Karavan automatically generates all component property editors using metadata provided by camel-catalog. Because of this universal approach, there isn't an existing extension mechanism for custom component-specific UI editors. 2. Component Updates: Once the PLC4X component is updated in Apache Camel with new parameters, descriptions, or enums, Karavan automatically picks them up in its next release directly from the updated catalog. 3. Release Alignment: Karavan’s release cycle aligns with Apache Camel LTS releases (since updating multi-user development servers monthly isn't practical for most teams). Of course, contributions are always welcome! Please feel free to ask any questions if there is anything else that could help you. Best, Marat On Tue, Oct 20, 2026 at 4:34 AM Christofer Dutz via dev < [email protected]> wrote: > Hi all, > > I'm currently working hard on integrating Apache PLC4X API into Apache > Camel and Apache Camel Karavan. > PLC4X has a number of features that would really help with setting up > connections, browsing tags, how they are fetched and possibly even > transformed. > Unfortunately Apache Camel Karavan provides only universal editors for > it's components. > > I would like to work on a PR for an extension point to allow plugins to > bring their own editors. > > Has this been discussed before? If yes, what was the outcome? Is there > already a mechanism that I missed that would allow me to do this already? > Does it make sense for me to work on such a PR? Would it be welcome? > > Chris
