I don't understand the ConfigTree constructor requirement exactly. If I deploy a custom action without a constructor that has a ConfigTree param, the esb throws an error at deploy time. However, if I extend AbstractActionPipelineProcessor, I'm not forced to include a ConfigTree constructor at compile time, which doesn't make any sense. It seems a little goofy that I have to tell everyone on my team "You have to have a ConfigTree constructor", but not actually enforce that in code. I'm planning on extending AbstractActionPipelineProcessor, but thought I might be missing something here. Can someone fill in the details? Thx.
