Mailing-List: contact dev-help@cocoon.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cocoon.apache.org
Mime-Version: 1.0 (Apple Message framework v619)
In-Reply-To: <5E091A68F794974CAF431CA31F5AF2CC11E95F@server.bizzdesign.nl>
References: <5E091A68F794974CAF431CA31F5AF2CC11E95F@server.bizzdesign.nl>
Content-Type: text/plain; charset=US-ASCII; format=flowed
Message-Id: <33564727-F147-11D8-9535-000A95782782@forthillcompany.com>
Content-Transfer-Encoding: 7bit
From: Brian McCallister <mccallister@forthillcompany.com>
Subject: Re: Javaflow status
Date: Wed, 18 Aug 2004 14:48:31 -0400
To: dev@cocoon.apache.org

Most people seem to be using ASM instead of BCEL anymore, since it is 
ASL now.

-Brian

On Aug 18, 2004, at 10:48 AM, Bart Molenkamp wrote:

> I also want to use Javaflow, but I think it's still a bit unstable, due
> to the BCEL libraries that are used (I guess). Just wondering, isn't
> there something else that can be used instead of BCEL?
>
> Another option you can use is Apples (see the samples). This seems to
> work very stable, but coding the flow is a little bit harder (IMO),
> since it cannot do a "sendPageAndWait()", but only a sendPage(), and
> after sending a page the process() cycle must return (I think that
> sendPage only sets the URL, which will be processed later by the apples
> interpreter). You can use the state design pattern to write your apples
> (see the woody/forms binding sample in particular).
>
> Bart.
>
> -----Original Message-----
> From: Ralph Goers [mailto:Ralph.Goers@dslextreme.com]
> Sent: Wednesday, August 18, 2004 4:40 PM
> To: dev@cocoon.apache.org
> Subject: Javaflow status
>
> I've looked through recent emails to try to determine what the status 
> of
> Javaflow is.  I've seen one issue that doesn't appear to be closed.  
> I'm
> wondering how stable this is as compared to the javascript version of
> flow.
>
> Due to the problems with using Rhino in weblogic we are seriously
> considering using javaflow instead, but I'd like to know what, if any,
> limitations there will be.
>
> Thanks,
> Ralph
>
>
>
>