Seam Scopes

[Rakesh Enoch]

Can someone please explain Conversation scope, Process scope in with some illustration. How did these originate and how better these are compared to other standard scopes.

[Michael Yuan]

Conversation is like a web wizard. It is a series of web pages inside a http session. It is smaller than a http session. It is especially useful in multiple browser tabs, where all tabs belongs to the same http session.

Process scope lives longer than the http session. It is a business process saved in the database. So, it can survive server reboots. And it can have multiple actors each having its own http session.

[Padmarag Lokhande]

Conversation scope falls between the request scope and session scope.
Normally the request scoped objects do not survive a redirect.
As opposed to this, Conversation scope maintains the objects even thorugh redirect.

[Rakesh Enoch]

Thanks guys. Probably I'll get a clear idea, after doing some coding and trying out some examples

[Jacob Orshalick]

If you get a chance to pick up the book, there are a number of illustrations in chapter 8, 9, and 10 describing conversation scope in-depth (from basic conversations, to concurrent conversations, and nest conversations). The process scope is also discussed in-depth in chapter 24.