Re: RFC: make JSExn non fatal and caught by Template.java

Brian Alliet wrote:

> On Mar 12, 2004, at 3:20 AM, Tupshin Harper wrote:
>
>>>> Right now, any template that has code that results in a JSExn 
>>>> effectively kills the application
>>>
>>> I think that is what we want. If a template application fails the 
>>> caller should know about it, right?
>>
>>  don't think think the current behavior is desirable at all.
>
>
> Oh.. I misunderstood what you meant by "application". I thought you 
> were talking about the application of an individual template. You are 
> talking about the application as in ibex as a whole. I agree with you 
> then. Ibex shouldn't get stuck in an "open but unresponsive state" if 
> the initial template fails. This is a bug.

So my two main motivations for catching JSExn in Template.java are to
1) Fix the "open but unresponsive" problem.
2) Have a central point that will log the source and line num of any JSExn.

Happy to address these in a different way, but catching in Template.java 
seemed the most elegant. Suggestions?

-Tupshin