[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-1352) Allow @Startup to be used on conversation scoped components

Mike Quilleash (JIRA) jira-events at lists.jboss.org
Fri May 25 14:29:08 EDT 2007

    [ http://jira.jboss.com/jira/browse/JBSEAM-1352?page=comments#action_12363228 ] 
Mike Quilleash commented on JBSEAM-1352:

I think so, they should probably only be created when a long running conversation starts.  If the component is needed for a temporary conversation then it should just be created manually.

If a @Startup component is already present in the conversation context when the conversation is begun then it's already created.

My personal use-case is for making sure components exist in the root of a conversation stack so create-on-begin works for me.

I can look at doing a patch if the above sounds reasonable.

> Allow @Startup to be used on conversation scoped components
> -----------------------------------------------------------
>                 Key: JBSEAM-1352
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-1352
>             Project: JBoss Seam
>          Issue Type: Feature Request
>          Components: Core
>    Affects Versions: 1.2.1.GA
>         Environment: Any
>            Reporter: Mike Quilleash
> @Startup on a conversation component would instantiate and call @Create the component whenever a conversation context is created (not when nested conversations start tho as the root conversation will already have created it).  Not sure if this should be done when a conversation context is created or when a long running conversation is begun.
> Use case is wanting to pass information from a nested conversation to it's parent, at the moment the parent has to explicitly instantiate any components it wishes to share with the child.  If the child creates it they get attached to the child conversation id and destroyed when the child ends.
> e.g. I want to pass FacesMessages (or some equivalent) from a edit screen to it's parent search screen when the edit is completed.  "Entity created/updated".
> A current workaround I think is to use the event stuff to have an @Observer in the relevant components to create themselves.

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