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 when rendering the own T5 error page?
Anyway, I don't have the required insight to trace the T5 rendering
mechanisms quickly, and unfortunately just now I don't even have the time to
make a view that reproduces it. (This does not happen under all
circumstances.)
I'll be back when I have time (if it is not solved yet) but atm my work is
too crazy...
- Ville
Code that crashes: (AbstractMarkupModel, 94)
public void encodeQuoted(String content, StringBuilder builder)
{
int length = content.length(); <-------
Ville Virtanen wrote:
>
> 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
>
> java.lang.NullPointerException
> at
> org.apache.tapestry5.dom.AbstractMarkupModel.encodeQuoted(AbstractMarkupModel.java:94)
> at
> org.apache.tapestry5.dom.Element$Attribute.render(Element.java:60)
>
>
>
--
View this message in context:
http://www.nabble.com/-T5--5.1.0.1-RC%2C-rendering-of-some-views-produces-stacktrace-tp22451299p22666415.html
Sent from the Tapestry - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
