[ http://issues.apache.org/jira/browse/VELOCITY-407?page=comments#action_12330603 ]
Tim Colson commented on VELOCITY-407: ------------------------------------- > VelocityViewServlet.getTemplate() method should append ".vtl" > to the URI by default (and only handle .vtl files in > its servlet-mapping clause). > So, a request http://www.foo.com/bar.html would map : > 1. to a template bar.html.vtl if found > 2. to a regular html file bar.html otherwise Pardon me if I am dense, but a servlet mapping for *.vtl -> V V S then *.html would NOT map to it, eh? And personally, I don't want to map *.html to V V S just so it can check to see if *.vtl exists. > Beyond the first basic samples, any webapp will need such a behaviour. > So all application designers will have to subclass VelocityViewServlet to do > it. I disagree. I have *.vm mapped to V V S and well...that's all I needed. If I wanted to use *.vtl...well, I could do that too with a mapping in the config. No change to V V S as far as I understand. And based on a principal of "least surprise"... I'd expect a file.html to go to the file.html or 404...not automagically go to file.vtl -- unless I specifically setup the mapping of *.html -> V V S myself. :-) > Templates vs. static content should be resolvable via file naming pattern > ------------------------------------------------------------------------- > > Key: VELOCITY-407 > URL: http://issues.apache.org/jira/browse/VELOCITY-407 > Project: Velocity > Type: Wish > Components: Tools > Versions: Tools-1.2 > Environment: all > Reporter: Claude Brisson > Priority: Minor > > The VelocityViewServlet.getTemplate() method should append ".vtl" > to the URI by default (and only handle .vtl files in its servlet-mapping > clause). > So, a request http://www.foo.com/bar.html would map : > 1. to a template bar.html.vtl if found > 2. to a regular html file bar.html otherwise > Beyond the first basic samples, any webapp will need such a behaviour. > So all application designers will have to subclass VelocityViewServlet to do > it. > Why not then incorporate it by default ? It looks rather important to me. > Having > to subclass the VelocityViewServlet for each and every project is really > silly. > Since there is a backward compatibility issue, one could trigger the > behaviour with > a configuration flag and wait for the tools 2.0 to have the default changed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
