Advice - Velocity or not?

[Mark Kaye <ma...@mkaye.co.uk>]

I am at a crucial stage in the development of a web app and wondered
what the opinions of the group were regarding the velstruts tool and/or
velocity in general.

I like the velocity way of doing things but I'm wondering whether or not
I should stick with JSP as this seems to be the primary view portion for
Struts.  I have velstruts working and it seems OK, but will I be losing
out on some flexibility by going down this route?

I am aware of the Velocity Struts (veltag) integration where velocity
type language can be used within a JSP page.  This is something I would
like to avoid as it strikes me as being a touch confusing.  My main
concern is to have a clean seperation of view and model.  Velocity
_feels_ like it gives me this (with velstruts not veltag), although I'm
not sure why in particular.

Thoughts anyone?  Are there any velstruts users here?

Rgds,

M

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>

Re: Advice - Velocity or not?

[Michael Delamere <ho...@michael-delamere.de>]

well,

we are actually doing it this way and are quite happy.  I personally didn´t
quite like the idea of JSP-tags looking exactly like HTML-tags.  I found it
difficult to tell the difference.  But that´s just my personal preference.

The only problem we are having currently with velstruts is that it is based
on struts1.0.2 and one of the developers mentioned that they would probably
start upgrading to 1.1 in October.

Just about everything works sweetly.  The only problems we are facing with
respect to the struts-version, is that it is ackward specifying the
forward-template when using multiple sub-applications.  The same goes for
the resource messages, whereby only the main application (default) resource
is being used by velstruts.  The recourse files belonging to the
sub-applications are currently being ignored.  I solved this however by
creating a custom RequestProcessor.

HTH.

Regards,

Michael


----- Original Message -----
From: "Mark Kaye" <ma...@mkaye.co.uk>
To: <st...@jakarta.apache.org>
Sent: Wednesday, September 11, 2002 5:21 PM
Subject: Advice - Velocity or not?


> I am at a crucial stage in the development of a web app and wondered
> what the opinions of the group were regarding the velstruts tool and/or
> velocity in general.
>
> I like the velocity way of doing things but I'm wondering whether or not
> I should stick with JSP as this seems to be the primary view portion for
> Struts.  I have velstruts working and it seems OK, but will I be losing
> out on some flexibility by going down this route?
>
> I am aware of the Velocity Struts (veltag) integration where velocity
> type language can be used within a JSP page.  This is something I would
> like to avoid as it strikes me as being a touch confusing.  My main
> concern is to have a clean seperation of view and model.  Velocity
> _feels_ like it gives me this (with velstruts not veltag), although I'm
> not sure why in particular.
>
> Thoughts anyone?  Are there any velstruts users here?
>
> Rgds,
>
> M
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>


--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>