That's actually the same file that was causing it for me. Huzzah for
the team effort!!!
It shall be solved!!!
- Charlie
On 2/4/06, Thomas E Enebo <[EMAIL PROTECTED]> wrote:
> > the actual content of what goes on pre/post method so much as changed
> > what class the code lives in.
> >
> > I'll be
> the actual content of what goes on pre/post method so much as changed
> what class the code lives in.
>
> I'll be getting back into RoR work tomorrow. Maybe you can zip up a
> sample dir that demonstrates the issue?
I have not figured out a reduced test case, but this single line
will make it
That could be an artifact from the original code; I haven't modified
the actual content of what goes on pre/post method so much as changed
what class the code lives in.
I'll be getting back into RoR work tomorrow. Maybe you can zip up a
sample dir that demonstrates the issue?
- Charlie
On 2/4/06
Yep...
Though the scope itself is there...the localValues is getting
set to null.
That also lead to another observation. We call
resetLocalVariables from AbstractMethod as long as the localNames
is not null (but could be empty). In resetLocalVariables we set
localValues to null if it is n
I ran into something similar when I was working on script/generate...a
Scope that had bogus local variables. I have not seen it recently, but
I think it's probably just a matter of popping too many scopes
(frames) or not initializing them correctly.
I assume it still fails with the AbstractMethod
Given a script:
require 'xsl/xmlparser'
I get error in Scope.getValue. It looks like we are popping back
down to an existing Scope and then calling resetLocalVariables on it
via DefaultMethod. This in turn nulls out localValues causing a NPE
in getValue.
It dies trying to access loaded on
