DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9649>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=9649 #include directive a bad choice... ------- Additional Comments From [EMAIL PROTECTED] 2002-07-08 23:05 ------- Yes, that is correct. The template is processed by the template before the web server reaches it because I'm using the templates to generate html from a servlet that gets sent to the web server. I would be able to escape the directive tags, however, there are certain components within our content management system that are velocity agnostic and spit out html with server-side includes. What I want to do is use the content management system (Vignette V/5 in this case) to house our velocity templates *and* still keep the component calls (left nav bars, etc) inside the Content Management System template. This way, if a component is changed from within the content management system, then the velocity template does not need to be altered. Since the component calls are in the V/5 Template language (TCL in this case), they look fine until they are rendered to Velocity template. The velocity template now contains web server #include directives (from the newly generated component) and I have to manually go in and escape all webserver #include tags to \#include tags. (that's if \# escapes the # character -- I only saw references to escaping variables in the user guide) I just think that Velocity would be more versatile if its #include directive were something else (perhaps #inc) so the lexer can easily distinguish the velocity include token from the web server include directive. Don't get me wrong, I think that Velocity is an EXCELLENT project and is in fact my favorite Templating system. :) I'm just trying to share an idea to help improve upon this already wonderful system. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
