Hi, I've got a quick question about making use of this for tooling.
I wonder if there would be such a way of getting access to the endpoint information without trying to instantiate the camel context and such? So that the tooling can be somewhat agnostic of Camel's instantiation process. Currently I have basic support for a plugin which can directly access the Component class by searching for for the relevant META-INF/services file with the component name. I wonder if it would be possible to then get access to the endpoint information directly from this class without instantiating core parts of Camel? IE would it be simple enough to attempt to statically analyse this class, or will instantiating Camel objects be the least painful way to do this? I'm also imagining that the endpoints might need some additional type information too, for instance if a String parameter should contain a FQCN or a bean name, or in the case of direct/vm/seda that it will link to another route. This kind of meta information would be great for performing validation/renaming/intellisense within the IDE! It would be great to hear any opinions about this :) Cheers, Alan -- View this message in context: http://camel.465427.n5.nabble.com/improving-Endpoint-documentation-and-tooling-tp5731334p5733219.html Sent from the Camel Development mailing list archive at Nabble.com.
