cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ralph Goers <Ralph.Go...@digitalinsight.com>
Subject RE: JXT or XSP?
Date Sat, 01 May 2004 16:20:10 GMT
You have to draw a line in the sand somewhere. Instantiating the objects
might not be so bad, but the next thing you know you'll be calling methods
on those business objects because its easy and then you'll really start to
pollute the controller with the model.

Ralph

-----Original Message-----
From: beyaNet Consultancy [mailto:beyanet@ntlworld.com] 
Sent: Saturday, May 01, 2004 9:11 AM
To: users@cocoon.apache.org
Subject: Re: JXT or XSP?

Ralph,
is there any particular reason why you don't instantiate business 
objects from within flowscript, or is purely preference that you don't?

Peter
On 1 May 2004, at 15:09, Ralph Goers wrote:

> I didn't mean to imply that there is no place for flowscript.  There
> certainly is.  As I said, we are using it.
>
> The controller in Cocoon is not the Actions; it used to be the entire
> sitemap. Now it is the sitemap + flowscript.  The problem is that it 
> is easy
> to have flowscript become part of the model and the view as well.
>
> When you look for doc on flowscript one of the first things you will 
> find
> are pages title "Advanced Flow Control".  That is really what 
> flowscript is
> for - managing flows that would be very painful to do in the sitemap. 
> For
> example, we have cases where the user requests a specific page and in 
> the
> process of generating it we discover that they must be presented with 
> some
> legal text that they have to accept or decline. Based on their 
> response we
> either display the requested page or send them somewhere else.  We 
> handle
> the "normal" request purely in the sitemap. When the alternate flow is
> detected the user is sent to another pipeline managed by flowscript. 
> While
> the alternate can be, and has been, managed directly in the sitemap, 
> this is
> a case where flowscript makes it a lot easier.
>
> What we don't do is instantiate or manipulate any business objects in
> flowscript.
>
> Ralph
>
> -----Original Message-----
> From: Christian Rosenberger [mailto:piepermail@gmx.de]
> Sent: Saturday, May 01, 2004 3:21 AM
> To: users@cocoon.apache.org
> Subject: RE: JXT or XSP?
>
> Hello!
>
> I think in concerns of MVC, the solution Ralph mentioned seems to be 
> the
> best. You have a clear seperation between prsentation, controller and
> business logic.
>
> The system would look like this:
>
> Presentation:  Plain XHTML or whatever output format you like
>
> Controller     Actions
>
> Modell:        Business Delegate/Business Logic Manager (connected to
> database in whatever way)
>
> All controlled in sitemap. As Ralph mentioned, if you put controlling 
> or
> logic in flowscript, the sitemap will loose all powerful possibilites 
> it
> has.
>
> Regards,
>
> Christian
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
> For additional commands, e-mail: users-help@cocoon.apache.org
>


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@cocoon.apache.org
For additional commands, e-mail: users-help@cocoon.apache.org


Mime
View raw message