DO NOT REPLY [Bug 43632] - NullPointerException in x:transform
| Newsgroups | gmane.comp.jakarta.taglibs.devel |
|---|---|
| Message-ID | <[email protected]> |
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43632>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=43632 ------- Additional Comments From [email protected] 2007-10-16 22:59 ------- Feels like a Sherlock Holmes mystery :) Nothing unsets t, so either it's being set to null, or it's not being set in the first place. The latter either because doStartTag is not being called, or because doStartTag is not reaching the 't = ...' line. 1) TransformerFactory breaking contract and returning null. 2) Container breaking contract and not calling doStartTag. 3) doStartTag throwing an Exception which is quietly caught. As nothing unsets t, I don't think concurrency would be at play, unless it's a bug relating to (2) above. I can't see anything in the Tomcat release notes post 5.5.17 about doStartTag. Only suggestion I have is to put tracing into the JSTL classes and try to hunt down which it seems to be. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.