I quickly discovered how I&#39;ve taken outjection for granted when I got started with the booking example. I instinctively created a @Producer methods to expose the hotels to the UI<br><br>&lt;h:dataTable value=&quot;#{hotels}&quot; var=&quot;_hotel&quot;&gt;...&lt;/h:dataTable.<br>
<br>   public<br>   @Produces<br>   @Named<br>   @RequestScoped<br>   List&lt;Hotel&gt; getHotels()<br>   {<br>      return hotels;<br>   }<br><br>However, the problem is that before the find() action gets a chance to invoke in response to the user clicking the Search button, JSF has already called on the &quot;hotels&quot; context variable and it is assigned to the request scope. So the UI doesn&#39;t see the updated value of the hotels property in the Render Response phase. If this method is on a session-scoped bean, you can perform a redirect after post and then the UI will get the right value.<br>
<br>What&#39;s the cleanest way to clear the context varaible in the find() method so that the producer runs again in the Render Response phase?<br><br>-Dan<br clear="all"><br>-- <br>Dan Allen<br>Senior Software Engineer, Red Hat | Author of Seam in Action<br>
<br><a href="http://mojavelinux.com">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction">http://mojavelinux.com/seaminaction</a><br><a href="http://in.relation.to/Bloggers/Dan">http://in.relation.to/Bloggers/Dan</a><br>
<br>NOTE: While I make a strong effort to keep up with my email on a daily<br>basis, personal or other work matters can sometimes keep me away<br>from my email. If you contact me, but don&#39;t hear back for more than a week,<br>
it is very likely that I am excessively backlogged or the message was<br>caught in the spam filters.  Please don&#39;t hesitate to resend a message if<br>you feel that it did not reach my attention.<br>