On Tuesday, March 4, 2003, at 11:46 AM, Bill Burton wrote:


Hello Geir!

Hello Bill!



Geir Magnusson Jr. wrote:
On Tuesday, March 4, 2003, at 12:58 AM, Tim Colson wrote:
To be make sure I'm clear: the modified proposal is to copy the
VelocityServlet code to Tools, opt. deprecate the core copy of
VelocityServlet, incorporate the Servlet section in the Velocity Main
Dev Guide into the Tools Dev guide, and have the Main docs simply point
to this new location?


Well, I guess what I was thinking was to *not* just move it, but start again - try to combine best practices in making something more useful for real life. I have stopped using the VelocityServlet because it doesn't do much for me in my real life.

+1


As a first step we could make it so VelocityViewServlet doesn't require subsclassing VelocityServlet and is resource based so it can be run from within a WAR with zero configuration.

> Rather, I use a servlet model
where introspection is used and the action is taken from the URL. It's really trivial, but it works for me.

You've mentioned that before. Sounds interesting and would make it much easier for people to get started using Velocity. Right now, it's a bit of a leap for beginners to go from VelocityServlet to an MVC framework.

I think I posted it to the list a while ago. I'm happy to do again if there's interest. I think it makes things even more confusion for people, because it pre-supposes you have a clue how servlets work, and are fine with the way it's being used. I will guess it isn't for everyone, and more sophisticated servlet developers won't like it. However, I wouldn't use anything else, because banging out simple UI's for the project I'm working on is just so easy.


Let me know if I should repost.

geir


-Bill



--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]


--
Geir Magnusson Jr                                   203-956-2604(w)
Adeptra, Inc.                                       203-247-1713(m)
[EMAIL PROTECTED]


--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]



Reply via email to