cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Oliver <res1c...@verizon.net>
Subject Re: [PROPOSAL] Continuation in objectModel, Was: Discussion of Flow Issues
Date Mon, 17 Mar 2003 04:15:45 GMT
Vadim Gritsenko wrote:
> Christopher Oliver wrote:
>> That's not the case. All are equally crippled ;) For example, when 
>> using  Xsp, the idea is that the only logic sheet you will ever use is 
>> the jpath logic sheet. This does not give you direct access to 
>> session, request, or context but only to the bean object. Likewise 
>> with XMLForm, you only have access to the bean itself. 
> 
> 
> 
> HUH?
> /me extremely puzzled
> 

Sorry, I'm not doing a better job explaining...

Since you responded to it I guess you did read this:

http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=103128978404439&w=2

I'm not saying anything different. To quote Ovidiu:

"The above explains how MVC could be really achieved in Cocoon with the
control flow layer. Note that there is no direct communication between
Model and View, everything is directed by the Controller by passing to
View a context object constructed from Model data. In a perfect world,
XSP should have only one logicsheet, the JXPath logicsheet. There
should be no other things in an XSP page that put logic in the page
(read View), instead of the Model. If you don't like XSP, and prefer to
use JSP or Velocity, the JXPath logicsheet equivalents should be
implemented."

Regards,

Chris


Mime
View raw message