If you are going to use the 2nd way, i would recommend checking out the Velosurf project.
That said, i honestly don't see anything kludgy about have a second servlet to handle form submissions. Updating the database and reading from it are two totally separate functions. Task division is perfectly normal and sensible. On 12/27/06, Matt L. <[EMAIL PROTECTED]> wrote:
I am using the VelocityViewServlet (VVS) and I would like to handle html form submission that will be writing to a database. What is the best practice/industry standard way of doing this? Just off the top of my head I can think of two ways. One would be to use an entirely different servlet to handle the form submissions. It's certainly more appealing to have everything going through the VVS - two servlets seems pretty kludgy to me.. I could also have a destination template read the parameters and, via a tool, write to the database. My concern there is that the Velocity template language may not be rich enough to pull off that level of functionality. I also wonder about performance. I'm sure there is something obvious that hasn't occurred to me. I looked in the documentation and searched online, but I didn't find anything to address this. Regardless, I apologize for asking such a basic question. Thanks, Matt -- View this message in context: http://www.nabble.com/VVS-Form-Submission---Best-Practices-tf2888050.html#a8068626 Sent from the Velocity - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
