I've been tracking the subject a little but still I do not get what is the current status of the matter so:
1. Will there be a possibility to call actions from flow ? 2. If not what should I do with a bunch of XSP actions if I wanted to use the logic in flow? <quote source="http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=105407572313285&w=2";> The migration path between Actions and flow is: move away from actions. Who? piece of cake: instead of using the Action interface, just implement your own service interface. that's it. Java components give services and these components should not be connected to cocoon. If you want, you can write a thin action wrapper around those components, but once you have the flow, I really don't see why you would go that way. </quote> So how could I migrate from ESQL intensive XSP actions to java components ? What is so bad in using actions in flow? ouzo
