title: JSF CDI : Conversation scope bean[s] best practice
body: <p>I'm currently learning about JSF 2.0 and im so glad for the existence of this conversation scope feature, which is very helpful in opening a new tab or a new window on the same page and having separate resources, not overriding one another.</p>
  
  <p>But im curious on how to implement this in a good way, about when to start the conversation and when to close it.</p>
  
  <p>In my case, i have each CDI bean for each JSF page. And let's say that i have a menu, and when it's clicked, this will lead to page A, and from A, could lead to B, B could lead to C, C could lead to D, all these 4 pages are connected in one chain. </p>
  
  <p>Accessing A's bean properties from B or C or D beans is possible, accessing B's properties is also possible from C or D beans and so forth.</p>
  
  <p>Now im quite confused about :</p>
  
  <ul>
  <li>whether all these A B C D should be
  in conversation scope or not, or
  perhaps just A ? Because i think
  sometimes from another page that is
  outside the ABCD chain, like a page
  F, it could navigate to page B,
  although i dont know how to supply
  the data to the bean B  yet.</li>
  <li>whether all these A B C D should be
  combined into one bean</li>
  <li>where and when to start the
  conversation, im thinking about the
  constructor, but i dont think it's a
  good idea, because i prefer starting
  the conversation when first accessing
  the page, not the bean</li>
  <li>where and when to stop the
  conversation, so that there wont be
  unused resources hanging around</li>
  </ul>
  
  <p>Please share your thoughts on this.</p>