Geir Magnusson Jr. wrote: >Tool loading like this can be dangerous depending on what can be specified >for the load. > If I understand, you correctly -- we are protecting the template developer by limiting the access they have. So, they don't or can't do something stupid like request 1,000,000 row result from a database. Gosh, this is so different from the Microsoft ASP world I'm comming from. In the Microsoft world, not only is this something you can do typically it is encourgaed by Microsoft in the MSDN examples. ;-)
>That said, I don't trust the controller author either, so I limit the tools available >:) > Sound like you have some trust issues ;) (Just kiddin') >First, you generally don't have to make 1 class per template. I am horribly >lazy, and generally have one controller servlet for my apps, and then >'action methods' are invoked within that servlet and they return the >template to be rendered (after filling the context with appropos data). So >the 1 class == 1 template can be easily avoided. > > Very True. Sorry, I worded that poorly. I know that need have the "controller" servlet, but I'm also really lazy. I don't even want to write that code, if I don't have too. If I understand things, this is where both Turbine and Struts come in. They provide the generic controller servlet framework. I'm working with Struts right now, because I have a few books on it. I looked at Turbine, but right now it bit overwhelming for a newbie. I figured I could come back an look at it for our next project. I know I need to learn it, before I can dig into Jetspeed. >VVS and Turbine aren't comparable. VVS isn't an application framework >(although you could build one around it). VVS was originally meant to be a >rendering servlet a la JSPServlet, so we could have a view system that could >be added to JSP-centric frameworks like Struts. > >Turbine is an application framework, with all the support one might expect. >It is a competitor to Struts. > I think you misunderstood me here. The impression I got from Jon's email was that there was a portion of this work already done in Turbine. He may have been talking about Bill's tool, I'm not sure. I understand that the goal is keep VVS application framework independant, which is something I like. I was just saying if there is any code we can reuse -- then lets look at it. If there isn't no big deal. As I said, I really lazy... ;) Thanks for the informative email, Jeff -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
