Return-Path: 
 <dev-return-44817-apmail-cocoon-dev-archive=cocoon.apache.org@cocoon.apache.org>
Delivered-To: apmail-cocoon-dev-archive@cocoon.apache.org
Received: (qmail 87471 invoked by uid 500); 13 Jul 2003 09:46:48 -0000
Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
list-help: <mailto:dev-help@cocoon.apache.org>
list-unsubscribe: <mailto:dev-unsubscribe@cocoon.apache.org>
list-post: <mailto:dev@cocoon.apache.org>
Reply-To: dev@cocoon.apache.org
Delivered-To: mailing list dev@cocoon.apache.org
Received: (qmail 87454 invoked from network); 13 Jul 2003 09:46:47 -0000
Received: from mail.gmx.de (HELO mail.gmx.net) (213.165.64.20)
  by daedalus.apache.org with SMTP; 13 Jul 2003 09:46:47 -0000
Received: (qmail 609 invoked by uid 65534); 13 Jul 2003 09:47:00 -0000
Received: from pD9EF42AF.dip0.t-ipconnect.de (EHLO WRPO) (217.239.66.175)
  by mail.gmx.net (mp012) with SMTP; 13 Jul 2003 11:47:00 +0200
Reply-To: <reinhard@apache.org>
From: =?iso-8859-1?Q?Reinhard_P=F6tz?= <reinhard_poetz@gmx.net>
To: <dev@cocoon.apache.org>
Subject: RE: calling actions from flow
Date: Sun, 13 Jul 2003 11:45:14 +0200
Message-ID: <000c01c34923$7700f3e0$af42efd9@WRPO>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.2627
Importance: Normal
In-Reply-To: <20030712143430.GA13737@mysza.ekom.net.pl>
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N



> -----Original Message-----
> From: ouzo@mysza.ekom.net.pl [mailto:ouzo@mysza.ekom.net.pl] 
> On Behalf Of Leszek Gawron
> Sent: Saturday, July 12, 2003 4:35 PM
> To: dev@cocoon.apache.org
> 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
>