Initial draw of JSP-generated table causes multiple JspTagExceptions on server using Spring.
Initial draw of JSP-generated table causes multiple JspTagExceptions on server using Spring.
lancex
Posts: 1Questions: 0Answers: 0
Hi, I've just started using DataTables a few weeks ago and think it's really cool. I'm currently using it on a table generated by Spring and if you never saw the logs on the server, you would say it's working perfectly. The thing is, it's causing the server to throw multiple JspTagExceptions from the class RequestContextAwareTag when (as far as I can tell) the table is initially drawn (the first pass) and is making the log pretty much useless. The generated page looks something like this:
http://live.datatables.net/erupif
The stack trace doesn't really reveal too much about what is going on but a coworker did point out this line:
[quote]at org.apache.jsp.jsp.errors._404_jsp._jspService(org.apache.jsp.jsp.errors._404_jsp:181)[/quote]
which suggests that datatables is trying to request a page that isn't there. AFAIK, I'm not telling datatables to use any server side processing so it shouldn't be contacting the server at all. I put it through firebug and figured out that it always happens when initializing the first and last columns. On the first column, it's thrown at line #4278:
[code]$(oSettings.aoColumns[i].nTh).addClass( sClass );[/code]
It also appears that an error is thrown here whenever sClass changes from "sorting_asc" to "sorting".
Then on the last column (or I suppose just after the table is initialized), I've narrowed it down to line #1763:
[code]nHolding.parentNode.replaceChild( oSettings.nTableWrapper, nHolding );[/code]
I can't imagine why either of those two lines should be causing the server to go haywire. I have not ran my code through the DataTables debugger as this is an internal web application and am a bit wary of letting it all out there but if there is anymore code that you would like me to provide, please ask and I'll see what I can do. Any help would be greatly appreciated! Thanks.
http://live.datatables.net/erupif
The stack trace doesn't really reveal too much about what is going on but a coworker did point out this line:
[quote]at org.apache.jsp.jsp.errors._404_jsp._jspService(org.apache.jsp.jsp.errors._404_jsp:181)[/quote]
which suggests that datatables is trying to request a page that isn't there. AFAIK, I'm not telling datatables to use any server side processing so it shouldn't be contacting the server at all. I put it through firebug and figured out that it always happens when initializing the first and last columns. On the first column, it's thrown at line #4278:
[code]$(oSettings.aoColumns[i].nTh).addClass( sClass );[/code]
It also appears that an error is thrown here whenever sClass changes from "sorting_asc" to "sorting".
Then on the last column (or I suppose just after the table is initialized), I've narrowed it down to line #1763:
[code]nHolding.parentNode.replaceChild( oSettings.nTableWrapper, nHolding );[/code]
I can't imagine why either of those two lines should be causing the server to go haywire. I have not ran my code through the DataTables debugger as this is an internal web application and am a bit wary of letting it all out there but if there is anymore code that you would like me to provide, please ask and I'll see what I can do. Any help would be greatly appreciated! Thanks.
This discussion has been closed.