[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2320) Query#refresh() should generate an event

Dan Allen (JIRA) jira-events at lists.jboss.org
Tue Jan 8 22:40:43 EST 2008

    [ http://jira.jboss.com/jira/browse/JBSEAM-2320?page=comments#action_12394253 ] 
Dan Allen commented on JBSEAM-2320:

Within the refresh() method in Query.java I suggestion putting:

if (Events.exists()) { Events.instance().raiseEvent("org.jboss.seam.refreshQuery." + getClass().getName()); }

We can either append the class name or use Seam.searchComponentName(getClass()) to resolve the name from the @Name annotation. There is still some limitation here since the EntityQuery class could be used multiple times via component configuration and there would be no good way to tell them apart.

> Query#refresh() should generate an event
> ----------------------------------------
>                 Key: JBSEAM-2320
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2320
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Framework
>    Affects Versions: 2.0.0.GA
>            Reporter: Dan Allen
>            Priority: Minor
>             Fix For: 2.0.x
>   Original Estimate: 1 hour
>  Remaining Estimate: 1 hour
> It is very useful to know when a query is refreshed, either because a parameter is dirty or because some other part of the application forced it to refresh itself. This message passing is extremely important when working in a caching situation.
> I am thinking something like:
> org.jboss.seam.queryRefreshed
> perhaps we pass the ejbql or the Query component as an parameter to the event

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the seam-issues mailing list