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

Michael Giroux commented on VELOCITY-527:
-----------------------------------------

I modified my code to include the original ParseErrorException as cause.  The 
actual exception is shown here.

In this case, the actual file name is 'session-facade-object.vm' so for 
purposes of this JIRA, we still have an issue. 

In addition, the column number reported as 17 is not exactly correct.  The #set 
line has two leading TAB characters, so I'm not sure if this should be column 2 
or 8, but certainly not 17.  Given whitespace issues, and use of TAB 
characters, it might not be possible to get column correct in any circumstance. 
 

Caused by: org.apache.velocity.exception.ParseErrorException: Encountered 
"#set" at line 273, column 17 of business
Was expecting one of:
    "[" ...
    "{" ...
    <STRING_LITERAL> ...
    "true" ...
    "false" ...
    <INTEGER_LITERAL> ...
    <FLOATING_POINT_LITERAL> ...
    <IDENTIFIER> ...
    "{" ...
    
        at 
org.apache.velocity.app.VelocityEngine.evaluate(VelocityEngine.java:311)
        at 
com.bull.eclipse.businesslayer.core.FileProducer.generate(FileProducer.java:649)
        ... 51 more

> Name of template truncated in error messages
> --------------------------------------------
>
>                 Key: VELOCITY-527
>                 URL: https://issues.apache.org/jira/browse/VELOCITY-527
>             Project: Velocity
>          Issue Type: Bug
>    Affects Versions: 1.5
>         Environment: Windows XP Pro SP2, JDK 1.5
>            Reporter: Michael Giroux
>
> Following was posted to mailing list:
> On 3/9/07, Will Glass-Husain <[EMAIL PROTECTED]> wrote:
> > Ouch.  Always hate that first bug report after a new release!
> > 
> > Would you mind please creating a JIRA issue at:
> > http://issues.apache.org/jira
> > 
> > On 3/9/07, Michael Giroux <[EMAIL PROTECTED]> wrote:
> > > I just upgraded to Velocity 1.5.  A key feature for me is the new
> > > functionality to include filename, line and column in error messages.
> > > When I was testing this feature with a faulty template, I discovered
> > > that the filename is being truncated. In the error message below, the
> > > actual file name should be "business-service-interface.vm"  It appears
> > > the parser truncated at the first "-".
> > >
> > >
> > > java.lang.Exception: Encountered "#else" at line 51, column 33 of business
> > > Was expecting one of: ...
> > >
> > >
> > > Michael:
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> > 
> > 
> > --
> > Forio Business Simulations
> > 
> > Will Glass-Husain
> > [EMAIL PROTECTED]
> > www.forio.com
> > 
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> > 
> > 

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