Hi Jeffrey, Whether or not events are helpful for your application really depends on your application. If you have components that know about each others' existence for the sole purpose of notifications, abstracting those exchanges into events is a clean way to decoupled those components.
The default AjaxRequestTarget event might be useful if you have a component that should be re-rendered with every request, but most AJAX workflows work fine with the standard mechanisms and do not call for refactoring. I don't think there are any particular "gotchas" with events, but making too many exchanges into events will just complicate your application. That was kind of vague question, but I hope my vague response helps! :) Dan On Mon, Oct 3, 2011 at 2:19 PM, Jeffrey Schneller < [email protected]> wrote: > I am currently converting an app to version 1.5.1 and am starting to > look into/work with the event model. What is the suggested approach for > using the event model? Should all Ajax be moved to the event model > (anywhere where in 1.4 the code had target.addComponent or > target.addJavascript calls)? > > > > Are there some areas of code that should not be using the event model? > Should/can feedback panels use the event model? > > > > Thanks for any advice. > > > > > >
