I've had this problem before as well, in my case it was related to a Label
component trying to render a label for a RadioGroup. Inside beginRender of
the Label component, it does this:
labelElement.forceAttributes("for", fieldId, "id", fieldId + ":label");
In my case, fieldId was null (as RadioGr
Ok, now I had time to look it little closer:
In the particular view I'm generating lazy initialization exp and observe
T5:
The String content is null and thus of course generates npe at that point.
the last encoded string (or one of those) is t-omitted-frame, so it actually
crashes somewhere whe
Hi, and thanks for the input.
I'll debug it, but currently other project that I'm working on is nearing
release so I'm tied to that one pretty much atm.
And I promise I'll try to get the alpha and RC names correctly in the future
;)
- Ville
luther.baker wrote:
>
> One suggestion ... downlo
One suggestion ... download and attach the source.
You could step through from the beginning of the request (can be tricky to
trace from the beginning with all the Javassist).
Or - at a minimum, you could jump to AbstractMarkupModel.java:94 and work
your way from there.
-Luther
On Thu, Mar 1
5.1.0.1 is not a release candidate. It's out there for exposure as an
alpha release (the vote isn't even completed yet!)
It looks like an issue with how null attributes are treated; assigning
an attribute (of a DOM Element) the value null is supposed to remove
the attribute entirely but it looks l
Hi,
We are constantly getting this stacktrace on some of our views. Nothing, and
I mean nothing else is visible. The normal T5 error page doesn't come up
etc. Only this stacktrace. Using 5.1.0.1-20090305.090208-13 everything works
ok.
Does anyone know how to trace this or dig deeper?
- Ville
