<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="gmail_quote"><div><div class="h5"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
KM> * Section 5.6.2 doesn't mention "flash" as an implicit variable, and I don't<br>
KM> see any other reference to how it is resolved in the PDF. The JavaDocs for<br>
KM> Flash say its an implicit variable called "flash".<br>
<br>
Fixed.<br>
<br>
KM> In addition, I would<br>
KM> expect "flash" to be "flashScope" like the other scope (even though it has<br>
KM> special semantics).<br>
<br>
For ease of use and convention with Rails.</blockquote></div></div><div><br>In that case, I think we should _also_ support flashScope. Otherwise it looks like we made a mistake to non-Rails developers. </div></div></blockquote>
<div><br>I agree. Why the heck are we catering to Rails developers? Sure, Rails presented an idea, but it doesn't mean we have to use the same name. Should we call JPA ActiveRecord? (I'm not saying they are the same, it's just a point). flashScope is the right name IMO.<br>
<br>-Dan</div></div><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'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't hesitate to resend a message if<br>
you feel that it did not reach my attention.<br>