Thank you Lance! This seems to be useful, but as far as I understand, it couldn't be possible to handle single Alert dismission, right?
Regards, Matias. On Wed, Jun 27, 2012 at 6:03 PM, Matías Blasi <matias.bl...@gmail.com>wrote: > Hi, I recently upgraded to tapestry-5.3.3, and I am trying to replace my > own user-messages component with the great Alerts one. > > My problem is that I need to know when a UNTIL_DISMISSED Alert is > dismissed. It is because I mark it as read in a database, because the > Alerts are generated for the users by an internal process either the user > is online or not. So, my Alerts has a 'target' attribute. I'm handling all > this logic pretty well, but I dont know how to override, or intercept the > dismiss operation, because it is not handled by a Service, it is resolved > between the Alerts component and the AlertStorage object. > > Suggestions will be appreciated. > > Regards, > Matias. >
