"baz" wrote : Very interesting thread. | i like to give a new usecase (or workflow) | We have a search screen, where the user can search for an object(e.g. an experiment) | When navigation to the show/edit screen ocurs a conversation is started and the object(the experiment) is shown. | | Now the user can work with the object(the experiment) | | What comes in now is a subworkflow. This workflow uses a nested conversation and could be started on any page. When this subworkflow ends, the nested conversation ends and redirection to the starting page occurs. | | (...) | | My question is how this kind of workflows can be correctly implemented with seam and conversations? For now, it seems to me that it is nessacary to deliver results from the nested conversation to the outer conversation. |
This exactly is the motive why I opened this tread: to request a better (or more elegant) way to transfer state (an ending result) back to the parent conversation when the nested conversation ends. >From a modeling perspective, it makes a lot of sense to model a use case (or >an activity or workflow) as a composition of sub use cases (or >sub-activities). For example, in UML use case diagrams you could define >include- or extend- relationships between use cases. In activity diagrams >it is possible to model the invocation of sub activities etc. When using Seam for the implementation, these models eventually would have to be mapped to Seam-based code. Clearly, Seam's nested conversation feature is somewhat limited as long as it is akward to transfer state back to the parent conversation (eg. if artificial POJO classes just for this state transfer have to be written). View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4086135#4086135 Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4086135 _______________________________________________ jboss-user mailing list [email protected] https://lists.jboss.org/mailman/listinfo/jboss-user
