Re: ! Exceptions in parsed templates are not thrown

["Geir Magnusson Jr." <ge...@optonline.net>]

On 8/31/01 11:24 AM, "Geir Magnusson Jr." <ge...@optonline.net> wrote:

> Sorry about delay...
> 
> Israel Strobel wrote:
>> 
>> Hello,
>> 
>> I already posted this some days ago, and I really need a solution.
>> 
>> I encountered following unexplainable behaviour:
>> 
>> Suppose you have a template (A) which parses another template (B) with the
>> #parse directive.
>> When A throws any Exception (ParseException or whatever, using an own method
>> which throws this exception) it is thrown to the
>> app, but if B throws any Exception it is only logged but _not_ thrown.
>> 
>> Is this a bug or can anybody explain why this happens ?
> 
> I think I answered this - I know what it is, and will do on the plane
> tomorrow if battery holds out :)
> 
> geir
> 

Ok - this is fixed - a MethodInvocationException, a ParseErrorException, and
a ResourceNotFoundException will all now be propogated to app level when
they happen in the course of a #parse()

geir

-- 
Geir Magnusson Jr.     geirm@optonline.net
System and Software Consulting
Developing for the web?  See http://jakarta.apache.org/velocity/
If you look up, there are no limits - Japanese Proverb