I am looking to move my web based mail application written using JSP and Beans to a
MVC model. I like what I see in Turbine and Velocity.
Any performance issues due to parsing the *.vm files? Or, is there some type of
caching involved?
Anyone have some good examples for the Turbine/Velocity combo?
>>> Jon Stevens <[EMAIL PROTECTED]> 02/06/01 01:00 PM >>>
on 2/6/01 3:29 AM, "Mica Davis" <[EMAIL PROTECTED]> wrote:
> If used properly, JSP fits the MVC model just fine.
Key words here. The problem is that JSP is almost NEVER used properly.
Even the examples on all of the javaworld.com articles on JSP don't use it
properly. What good is that?
> Your always going to have some type of code in your
> presentation level. Whether it is VTL or Java
> shouldn't matter. VTL is still code...Try to teach a
> creative designer how to write VTL. You'll have no
> more luck than trying to teach them Java basics.
Actually, that is where you are wrong. There are very fundamental
differences between VTL and "code". VTL has a well defined small subset of
functionality that prevents it from being used improperly, where with JSP
you must actually make more effort to use it improperly.
> What is the difference between:
Your example is fundamentally flawed in that you are not giving an example
of a pull based application. What you should really do is provide an example
of doing that with a pull based system. You missed all the parts where, in
your JSP page, in order to do pull based systems, you have to do things like
this:
<jsp:useBean id="cart" scope="request"
class="com.mycompany.MyApp.MyCart"/>
Ok, right there, you have screwed up the View portion of the model because
you are embedding the scope of the use of the bean within the
template...that is not part of the View!!!! This is not something that a
designer wants to know about or can even know about. Let me also state that
the syntax of that blows. What designers are going to actually remember how
to type all of that?
> Personally I would rather use java. VTL is clunky.
Right, but you know how to write Java. That is where you just totally missed
the boat. Your designers don't know how to write Java and therefore VTL is
much easier for them.
-jon
--
If you come from a Perl or PHP background, JSP is a way to take
your pain to new levels. --Anonymous
<http://jakarta.apache.org/velocity/> | <http://java.apache.org/turbine/>
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/[email protected]/>
List Help?: [EMAIL PROTECTED]
