You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@velocity.apache.org by Daniel Rall <dl...@collab.net> on 2001/03/27 00:45:39 UTC

Re: More torque anguish

carl@destinymusic.com writes:

> ...
> Mon Mar 26 14:28:04 PST 2001  [error] Method parse threw exception for reference $generator in template om/Control.vm at  [41,9]

It would be helpful if the InvokationException indicated *why* the
exception was thrown.  I haven't looked closely enough to see if this
is easily possible...

Daniel

Re: More torque anguish

Posted by Daniel Rall <dl...@collab.net>.

"Geir Magnusson Jr." <ge...@optonline.net> writes:

> Daniel Rall wrote:
> > 
> > carl@destinymusic.com writes:
> > 
> > > ...
> > > Mon Mar 26 14:28:04 PST 2001  [error] Method parse threw exception for reference $generator in template om/Control.vm at  [41,9]
> > 
> > It would be helpful if the InvokationException indicated *why* the
> > exception was thrown.  I haven't looked closely enough to see if this
> > is easily possible...
> 
> Like a .wav file or something, so you can listen to an explination? :)

Heh.

> The MethodInvocationException contains :
> 1) the original exception thrown by your method so you can dig it out
> and look at it.
> 2) the method name that threw it
> 3) the reference used in the template to access the method
> 
> and the log contains the template and line/col where it occurred.
> 
> What else would be good to have?

I was speaking of #1.  I guess I didn't associate the huge stack trace
above the message with the IE...oops.

Daniel

Re: More torque anguish

Posted by "Geir Magnusson Jr." <ge...@optonline.net>.

Daniel Rall wrote:
> 
> carl@destinymusic.com writes:
> 
> > ...
> > Mon Mar 26 14:28:04 PST 2001  [error] Method parse threw exception for reference $generator in template om/Control.vm at  [41,9]
> 
> It would be helpful if the InvokationException indicated *why* the
> exception was thrown.  I haven't looked closely enough to see if this
> is easily possible...

Like a .wav file or something, so you can listen to an explination? :)

The MethodInvocationException contains :
1) the original exception thrown by your method so you can dig it out
and look at it.
2) the method name that threw it
3) the reference used in the template to access the method

and the log contains the template and line/col where it occurred.

What else would be good to have?

geir

-- 
Geir Magnusson Jr.                               geirm@optonline.net
Developing for the web?  See http://jakarta.apache.org/velocity/