> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] > On Behalf Of Leszek Gawron > Sent: Saturday, July 12, 2003 4:35 PM > To: [EMAIL PROTECTED] > Subject: calling actions from flow > > > 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 ?
Expect it to be part of the "legacy support" of the Flow implementation (not implemented yet). > 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=10540 > 7572313285&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? Many people think that actions are not the right place to put in your business logic. From a technical POV you can do whatever you want (do matcher tasks, control your application, integrate your backends, ...) and this is some sort of mess. But other think that this is no problem. Therefore we provide legacy support to integrate your existings actions. > ouzo >
