1 Reply Latest reply on Feb 10, 2007 10:42 AM by gavin.king

    Never ending conversation

      I have a search page where I want to isolate two instances of the search screen from each other so the user can have two tabs open on the same page and be searching for different things. I store a fair amount of state (pagination, grid model etc) so the conversation scope made sense for this.

      I added @Begin to my @Create method and it worked fine, but now I don't really have anywhere to put @End because a search page conversation never really ends. The conversation will timeout eventually if left idle for long enough which is also fine. Is this lack of @End ok to do?

      I looked at the Seam booking example but it seemed to be using session scope for the searching rather than conversation.