> Yes, I fully support the concept that business logic ist kept strictly > separated form the view. However, there are applications where some > logic is needed in the view (view logic not business logic). A typical > example is client side form validation. That's what we are trying > to support.
But why don't you set the parameters on the JSP side and then pass a facade to Velocity? Or why don't you put properties in such facade, in such a way that you can set them one by one instead of passing them all as parameters? Have fun, Paulo Gaspar > -----Original Message----- > From: Gabriel Sidler [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 28, 2001 7:24 AM > To: Velocity Developers List > Subject: Re: #macro functionality > > > Paulo Gaspar wrote: > [..] > > > 2) Much effort has been invested into developing JSP custom tag > > > libs. Some of them have been proven to be very useful. For many > > > of the custom tag libs the source is openly available. It would > > > be very interesting if Velocity were able to use the > > > implementations of the existing custom tag libs. A superficial > > > investigation shows that this might be "quite" easy to achieve. > > > Any ideas on this? > > > > One of the strongest ideas behind Velocity is that logic should be > > kept separated from presentation. Taglibs are one way how logic is > > NOT separated from presentation in JSP. > > Yes, I fully support the concept that business logic ist kept strictly > separated form the view. However, there are applications where some > logic is needed in the view (view logic not business logic). A typical > example is client side form validation. That's what we are trying > to support. > > Gabe > > > > -- > Gabriel Sidler > Software Engineer, Eivycom GmbH, Zurich, Switzerland -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
