[ 
https://issues.apache.org/jira/browse/VELOCITY-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484856
 ] 

Christoph Reck commented on VELOCITY-535:
-----------------------------------------

The parse error indicates that some construct is not complete (an #if of 
#foreach without a corresponding #end). 

It would be helpful if the velocity parser would point to the start of this 
construct istead of the current message.

In the middle of the most indented level I see a probable cause:
      #end
      #else
both at the same level... I don't see the #if for this #else...

Further down are two #end statements, also at the same innermost level.


This should not have been posted to the Velocity-bugtracker, better place would 
have been the [email protected]


> org.apache.velocity.exception.ParseErrorException: Encountered "<EOF>" at... 
> -----------------------------------------------------------------------------
>
>                 Key: VELOCITY-535
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-535
>             Project: Velocity
>          Issue Type: Bug
>          Components: Engine
>    Affects Versions: 1.5
>         Environment: Windows Xp-Vista-Srv 2003; JDK1.5.0_11;Tomcat 5.5.17; 
> Struts 2.0.6
>            Reporter: Jean Seurin
>         Attachments: SearchSchedule.vm
>
>
> Suddenly receive a org.apache.velocity.exception.ParseErrorException: 
> Encountered "<EOF>" at line (last line, last char of the template) for the 
> attached template.
> No particular reason, it used to work perfectly. It doesn't not anymore, 
> whatever I put at the end of the template (##, several blank lines, etc...)

-- 
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