Screen classes where a requirement before templating languages like Velocity and JSP where available. IMOHO, Screen classes are not very MVC oriented as they put to much programming logic behind a specific template page. In the past, Screen classes used ECS to physically build the HTML pages for the View.
There are to ways to approach this: 1. Standard MVC using Actions and ActionEvents. The template a.k.a. the View, can be set with in your Action or directly using request parameters or path info. Actions can always override the template specified in a request. If you are familiar with Struts, here is direct comparison. Turbine Action = Struts' Action and Turbine ActionEvents = Struts' DispatchAction So in MVC terms: Model: I suggest using Fulcrum services or a standard singleton pattern for abstracting business logic. View: Velocity templates or JSPs Controller: The Turbine servlet and the Turbine Action/ActionEvents. 2. Turbine Model 2+1 MVC paradigm. It is very similar to the MVC except you make extensive use of pull tools to bring business logic into your templates. Read: http://jakarta.apache.org/turbine/turbine-22/model2+1.html for more detail on Model 2+1 hth, Scott > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]] > Sent: Tuesday, December 31, 2002 12:24 PM > To: Jetspeed Users List > Subject: what happened to velocity screens? > > I have a fairly huge turbine application (30+ screens) that I would like > to integrate into jetpeed. It's using velocity templates. > > Right now, I do have SSO going on, that is, if I login to the portal, I > can then go right into my application, but I would like a tighter > integration, like Oracle's JSPRenderer for a portlet type of thing. > > Anyway, I would like any thoughts on how to integrate a application like > this to jetspeed, and ... I took a good read, and I see the Action > classes, but I do not see anything for the Screen classes, that is, how do > I prepare the context before the view. Does everything happen in an > Action? Isn't this kinda breaking the MVC paradigm? > > Thanks. > > > -- > To unsubscribe, e-mail: <mailto:jetspeed-user- > [EMAIL PROTECTED]> > For additional commands, e-mail: <mailto:jetspeed-user- > [EMAIL PROTECTED]>
