STP/EID Component/EID Developers
I'm working on this bug to add (quickly) generation capabilities for Apache Camel. There will be a tutorial on it at EclipseCon 2008, that's why it's being done quickly :) As I go along, I'm taking some development notes for reproduction here.
EID extracts all the models from the org.eclipse.stp.eid/componentModel directory and puts them into a .cimero2 directory in your home.
Next, each component in the .cimero2 is opened, scanned, and there is an attempt to detect the ESB to which that component belongs to see if it is the same as the one that has been chosen at startup time.
If a component is offered by the chosen ESB, a component model gets created in memory including the name for the component, what ESB it belongs to, the icon for it and the component type. Then it's added to the list of component models, which gets reflected on the palette (see org.eclipse.stp.eid.Parser).
Because of the way this is done, you can add your very own component model definitions in this directory, and they will be available on the palette when the canvas starts up.
Once you have created the graph of connected component models, you are in a position to generate configuration. At the moment, it's not easy to see what properties are missing, etc. When you choose a generation option, it eventually all goes through a single choke point org.eclipse.stp.eid.generator.GeneratorImpl, which initially creates a directory structure, then kicks off specific JET templates to construct the various configuration elements in the appropriate places.
One thing here is that JET is set up to create the Java files at runtime and then Eclipse compiles them and uses them to generate the configuration. This has the advantage of allowing people to jump into the plugin and change the template, but it does slow things down and it means that it is very difficult to run this headless. Also, it's using an old version of JET, i.e. not JET2.