-
Feature Request
-
Resolution: Done
-
Major
-
None
-
None
Unless Camel find a way to get rid of this limitation, the tooling need to be provide a validation on ids:
invalid use case:
<from id="myId" uri="myId:XXX"/>
valid usecase (even if I'm not sure to understand why this one is more valid):
<from id="myId1" uri="myId2:XXX"/>
<from id="myId2" uri="whatever:XXX"/>
more complex invalid usecase with "cyclic dependency seems possible. the best would be to have an API in Camel providing the validation (and will be a very nice candidate for LSP Camel validation ^^)
- is related to
-
FUSETOOLS-2560 Provide warning validation when a component is the same than an existing component definition id from the catalog
- Open
- relates to
-
ENTESB-8254 XML Routes do not load when a camel component id is similar to a camel component definition id
- Closed
-
FUSETOOLS-2578 Upgrade from Camel 2.19.x to 2.20.1
- Closed