does anyone have an example to contribute to wicket-examples that shows
how to use ajaxhandler?
the current ajax prototype example looks really nice and does not need
to use doRender(). looking
at that example, i wonder if doRender() should really exist. it's quite
elegant to set the request target.
what is it again that can you achieve with doRender() that you cannot
achieve by setting the request
target?
also, i noticed these settings in the form example and in the ajax example:
getExceptionSettings().setThrowExceptionOnMissingResource(false);
getRequestCycleSettings().addResponseFilter(new
ServerAndClientTimeFilter());
they seemed like they should be pushed up into WicketExampleApplication
so that all examples include
these settings as defaults. is there any reason not to do this?
jon
Eelco Hillenius wrote:
and the target does not allow to render multiple components.
Why not? IRequestTarget is an interface that can be implemented in any
way. If you want it to render two components, implement one that does
that.
Eelco
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&opÌk
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_idv37&alloc_id865&op=click
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
