It would be good if we could just rely on Spring's class path scanning capabilities to find workflow beans, and map their methods from that. It's a pain having to register them all in the Workflow implementation, and creates excessive dependencies.
In fact maybe we can retire the workflow class completely?
We need to HelpMessageConsumer to do it's own introspection.
It should look up all beans with the @Work annotation from the ApplicationContext and build a help menu using that.
It would be good if we could just rely on Spring's class path scanning capabilities to find workflow beans, and map their methods from that. It's a pain having to register them all in the Workflow implementation, and creates excessive dependencies.
In fact maybe we can retire the workflow class completely?