[ 
https://issues.apache.org/jira/browse/VELOCITY-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564139#action_12564139
 ] 

Christopher Schultz commented on VELOCITY-584:
----------------------------------------------

Since the built-in "include" directive requires parameters, maybe that could be 
the way to determine what Velocity does.

Since #include requires an argument, any bare references to #include could be 
ignored because the reference doesn't "match" anything that exists in the 
directive or marco lookup table.

This would be kind of like calling a method in a programming language without 
the right arguments in the right order. The default behavior for handling 
"inappropriate" directive or macro invocations would be to simply print out the 
original text (just like when we can't find an appropriate variable or other 
reference).

I don't know if this is possible, but it sounds at least plausable.

> Change the #include directive ignore the SSI version of include
> ---------------------------------------------------------------
>
>                 Key: VELOCITY-584
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-584
>             Project: Velocity
>          Issue Type: Improvement
>          Components: Engine
>    Affects Versions: 1.5
>            Reporter: Tim White
>
> When processing a file that happens to have the SSI version of 'include' in 
> it, the velocity engine breaks.
> There are many cases where we end up with files that contain both, before 
> they are cleaned up.
> <!--#include file="wisdom.inc"-->
> Essentially, if it sees that syntax, it needs to ignore the include.  A 
> suggestion would be to check for any amount of whitespace after the #include, 
> and then "file=".  I don't think that will step on proper Velocity include 
> syntax.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


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

Reply via email to