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

Allow @Startup to be used on conversation scoped components ----------------------------------------------------------- Key: JBSEAM-1352 URL: http://jira.jboss.com/jira/browse/JBSEAM-1352 Project: Seam Issue Type: Feature Request Components: Core Affects Versions: 1.2.1.GA Environment: Any Reporter: Mike Quilleash Fix For: The future Attachments: conversationstartup.patch @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.