Results 1 to 5 of 5

Thread: conversation scope

  1. #1
    Join Date
    Sep 2007
    Posts
    5

    Default conversation scope

    hi all, I have read about the web flow documentation
    but i am not quite sure about the conversation scope...

    I would like to know when exactly is a bean in conversation scope goes out of scope...
    after a bindAndValidate() of the assocaited formAction?

    after a form submission with that bean,
    i found that subsequent form with the same formAction is populated with the previously entered value...
    is it the form still associated with the same bean?
    or is it required that i call resetForm() manually after every form submission?

    thanks.

  2. #2
    Join Date
    Jun 2006
    Location
    The Netherlands
    Posts
    13,625

    Default

    hi all, I have read about the web flow documentation
    Read closer. The different scopes are clearly explained...

    REQUEST - Object destroyed after request
    FLASH - Object destroyed after request-response cycle
    FLOW - Object destroyed when flow finishes
    CONVERSATION - Object destroyed when the conversation finishes.

    Request is the shortest lived, Conversation the longest...
    Marten Deinum
    Java Consultant / Pragmatist / Open Source Enthousiast / Author


    Pro Spring MVC: With Web Flow
    Conspect

    Have you read the reference guide.
    Use the [ code ] tags, young padawan

  3. #3
    Join Date
    Nov 2008
    Posts
    2

    Default

    Hi guys, I think there is a big confusion around the scopes, I've googled around for a couple of days trying to find a spring definition , because the ones in the documentation are not clear enough.

    I understand this:

    CONVERSATION - Object destroyed when the conversation finishes.

    But is there a Spring definition for "conversation" in the documentation?

    What's the difference between this scopes and the Seam scopes?

    In my case I need a different session for each browser tab, and I'm still not sure how to implement this with Spring Webflow but I've heard that it's possible with Seam.

  4. #4
    Join Date
    Apr 2009
    Posts
    1

    Default

    Is there anything more written about it? I'm solving the same problem with session (conversation) for each panel.

  5. #5
    Join Date
    Nov 2008
    Posts
    742

    Default

    I'm assuming you understand how flow scope works. If a flow is invoked explicitly, NOT as a subflow, then it is a top-level flow, and starts a new conversation. The conversation (and attributes in conversation scope) last for the duration of the top-level flow and any subflows it calls. When a top-level flow ends, the conversation ends and conversation scope is cleaned up.

    If you do a flow-redirect in the top-level flow's end-state, then you are ending one conversation (and cleaning up conversation scope) and starting another, with a new top-level flow.

    Hope this helps.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •