On Wed, 21 Feb 2001, Geir Magnusson Jr. wrote:
> Was doing a little review of this, and the problem really isn't centered
> around Template.merge() - rather Runtime.getTemplate() may be where we
> should focus.
>
> getTemplate() currently returns a healthy, working Template or null,
> null when it can't find the resource (file) or parse it due to syntax
> error. Now, that hides the reason (although it is logged...)
>
> How about we create a new set of exceptions :
>
> org.apache.velocity.exception.ResourceNotFoundException
> org.apache.velocity.exception.ParseErrorException
>
> to get started, and have getTemplate() throw those. That basically are
> the two problem conditions that are really common and predictable with
> this, and it would make the Turbiners happy.
>
> I am suggesting the new package o.a.v.exception, as we have a
> o.a.v.runtime.exception package already, but that is for internal stuff,
> and o.a.v.runtime.parser.ParserException, but again, that's internal for
> the most part.
>
> Maybe o.a.v.app.exception ? Maybe that's better.
I think o.a.v.Exception is fine.
jvz.
