Project

General

Profile

Bug #1047

WTextEdit. NullPointerException in 2nd rendering phase

Added by Thim Anneessens almost 10 years ago. Updated almost 10 years ago.

Status:
InProgress
Priority:
Low
Assignee:
Pieter Libin
Category:
-
Target version:
-
Start date:
11/03/2011
Due date:
% Done:

0%

Estimated time:
0.50 h

Description

Hello it is quite difficult to debug when errors are thrown in the second rendering phase.

I had the problem with WTextEdit. Apparently setText() has a preconditions: text must not be null. This is however not document and not checked. Could you add the checking on set?

Best regards,

Thim.

#1

Updated by Thim Anneessens almost 10 years ago

Here is the stack trace that I had:

java.lang.NullPointerException

at eu.webtoolkit.jwt.StringUtils.sanitizeUnicode(StringUtils.java:297)

at eu.webtoolkit.jwt.WWebWidget.escapeText(WWebWidget.java:811)

at eu.webtoolkit.jwt.WWebWidget.escapeText(WWebWidget.java:823)

at eu.webtoolkit.jwt.WTextArea.updateDom(WTextArea.java:244)

at eu.webtoolkit.jwt.WTextEdit.updateDom(WTextEdit.java:250)

at eu.webtoolkit.jwt.WWebWidget.createDomElement(WWebWidget.java:719)

at eu.webtoolkit.jwt.WWebWidget.createActualElement(WWebWidget.java:755)

at eu.webtoolkit.jwt.WWidget.createSDomElement(WWidget.java:1306)

....

#2

Updated by Pieter Libin almost 10 years ago

  • Status changed from New to InProgress
  • Assignee set to Pieter Libin
#3

Updated by Pieter Libin almost 10 years ago

We will check for each String argument that is passed to the public API that it is not null.

Also available in: Atom PDF