velocity-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Will Glass-Husain (JIRA)" <j...@apache.org>
Subject [jira] Commented: (VELOCITY-98) #parse / #include causing ClassCastException
Date Wed, 04 Jan 2006 05:44:00 GMT
    [ http://issues.apache.org/jira/browse/VELOCITY-98?page=comments#action_12361710 ] 

Will Glass-Husain commented on VELOCITY-98:
-------------------------------------------

The problem reappeared once we changed the Exception handling code to pass through RuntimeExceptions.
 (hooray for the regression test case which suddenly started failing.)

I've applied Michal's patch.  Thanks for contributing!

> #parse / #include causing ClassCastException
> --------------------------------------------
>
>          Key: VELOCITY-98
>          URL: http://issues.apache.org/jira/browse/VELOCITY-98
>      Project: Velocity
>         Type: Bug
>   Components: Source
>     Versions: 1.3-rc1
>  Environment: Operating System: Linux
> Platform: All
>     Reporter: Simon Christian
>     Priority: Minor
>      Fix For: 1.5

>
> If caching is on, and a template has been previously cached due to a #parse or 
> #include directive, subsequently using the other directive will cause a 
> ClassCastException and fail.
> Example: if I have two templates, the first one loaded includes the line:
>   #include( "include/header.vtl" )
> and the second one the line: 
>   #parse( "include/header.vtl" )
> When the second page is viewed, a ClassCastException is thrown with an error in 
> the log like:
> [error] #parse() : arg = include/header.vtl.  Exception : 
> java.lang.ClassCastException: 
> org.apache.velocity.runtime.resource.ContentResource
> A solution might be to include the resourceType as part of the key when 
> caching/retrieving the resource, within the getResource() method of the 
> org.apache.velocity.runtime.resource.ResourceManagerImpl class. Alternatively 
> seperate caches could be used for the different types of Resource.

-- 
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: velocity-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: velocity-dev-help@jakarta.apache.org


Mime
View raw message