Re: [Wicket-develop] NPE in displaytag.ExampleExport

Eelco Hillenius Wed, 01 Dec 2004 02:59:03 -0800

Ok, the possibility of not having a page to render is new to me, but in this case it seems like a valid use. If there's no objections, I'll build some null checks that handle this problem.

Eelco

Juergen Donnerstag wrote:

 If I then choose the DisplayTags exmaples, then the ExampleExport,
then Export to CSS, I get a Null Pointer Exception showing up in
HttpRequestCycle.

 What seems to be happeing is that the rendering for 0.exportCSV does
a setPage(), then invokes the 'linkClicked" method on the ExportLink
component, which does a setPage(null), but when the rendering gets to
the 'finally' block in RequestCycle, there's no check in either the
call to or the implementaton of 'detatchModels(page)', which gives the
NPE.

 A check, either in the call or the body, fixes the problem, but I'm
not sure if it's the real problem or showing something else up -
comments?


ExportLink.linkClicked() sets the page == null in order to prevent any
page rendering (the response contains the export data not the page
rendered). This worked fine so far.  RequestCycle.render(), especially
the finally block however depends since recently on a valid page.
Currently I don't see other means to return the export data and
prevent rendering the page. Thus, the finally block should  not rely
on a valid page variable.

regards Juergen

------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Wicket-develop mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/wicket-develop

Re: [Wicket-develop] NPE in displaytag.ExampleExport

Reply via email to