[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-3195) Support for @Observer in Wicket classes

Clint Popetz (JIRA) jira-events at lists.jboss.org
Tue Nov 18 14:10:36 EST 2008

    [ https://jira.jboss.org/jira/browse/JBSEAM-3195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12438791#action_12438791 ] 

Clint Popetz commented on JBSEAM-3195:

I'm not sure how this would work.  WickeComponents aren't really full-fledged seam components; their lifecycle is not managed by Seam, and they aren't bound to a context.  So while I could have WicketComponent register methods marked @Observer with Init's list of observers, there's no way to find the actual instance of that component to invoke the method upon at event time.

The only path towards this I could see would be to actually make Wicket component instances live in seam's session context (because they do have a session lifetime in Wicket's pageMap.)  This could be done, but afaict the only benefit would be @Observers, because I don't think you'd ever want to inject an instance of a wicket component into another object.  (It would be like injecting a JSF UIComponent subclass, which I see no use for.)

I'll leave this issue open to hear other's thoughts on it.

> Support for @Observer in Wicket classes
> ---------------------------------------
>                 Key: JBSEAM-3195
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-3195
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Wicket
>            Reporter: Pete Muir
>            Assignee: Clint Popetz
> Don't know if this is good or not

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


More information about the seam-issues mailing list