Yeah, I get that we want people to do it the new way. I just hate to undo some of the convenience features we provided in the past for when you have no choice but to do it the old way. I'm skeptical I will win this debate though.<br>
<br>-Dan<br><br><div class="gmail_quote">On Fri, May 8, 2009 at 3:19 AM, Gavin King <span dir="ltr"><<a href="mailto:gavin.king@gmail.com">gavin.king@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I really don't think this is a good idea. We should be encouraging<br>
people to use the New Way.<br>
<div><div></div><div class="h5"><br>
On Fri, May 8, 2009 at 2:18 AM, Dan Allen <<a href="mailto:dan.j.allen@gmail.com">dan.j.allen@gmail.com</a>> wrote:<br>
> On Thu, May 7, 2009 at 9:06 AM, Gavin King <<a href="mailto:gavin.king@gmail.com">gavin.king@gmail.com</a>> wrote:<br>
>><br>
>> Right.<br>
>><br>
>> Contextual is there so that frameworks can put stuff in contexts for<br>
>> "special" cases.<br>
>><br>
>> It's not really meant to be used by application code or "normal"<br>
>> framework code. Stick the stuff in a bean, or use a producer method.<br>
><br>
> So the question was also brought up whether we should provide the unified<br>
> API to the standard attribute maps in the Servlet and JSF APIs. Ideally, of<br>
> course, you are using beans and producer methods to populate these contexts.<br>
> But one of the major usability improvements provided by Seam was the fact<br>
> that you had one way to access all contexts. Given that we have all been<br>
> involved in writing applications for companies, you should know as well as I<br>
> do that it's extremely common to have to use these attribute maps for one<br>
> thing or another. It's life. Clint said in the meeting you can always just<br>
> get a handle to that map the regular way. Let me remind you how this is done<br>
> in JSF:<br>
><br>
> application scope:<br>
> FacesContext.getCurrentInstance().getExternalContext().getApplicationMap()<br>
> request scope:<br>
> FacesContext.getCurrentInstance().getExternalContext().getRequestMap()<br>
> session scope:<br>
> FacesContext.getCurrentInstance().getExternalContext().getSessionMap()<br>
> view scope: FacesContext.getCurrentInstance().getViewRoot().getViewMap()<br>
> flash scope: very bizarre mix of request map and some internal state<br>
><br>
> All I'm saying is that I think Seam should provide producers that expose<br>
> these maps so that they are injectable (as the type AttributeMap). I'm not<br>
> saying we use these maps to manipulate or access beans. This is for<br>
> integration with legacy systems, storing data ad-hoc in a non-JSR-299 way,<br>
> or whatever else the case may be. The question is going to come up and I<br>
> think people will just look for solutions elsewhere (<a href="http://sourceforge.net" target="_blank">sourceforge.net</a>) to<br>
> patch Seam to provide something like this. It's not perfect. It's life.<br>
><br>
> -Dan<br>
><br>
> --<br>
> Dan Allen<br>
> Senior Software Engineer, Red Hat | Author of Seam in Action<br>
><br>
> <a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br>
> <a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br>
> <a href="http://in.relation.to/Bloggers/Dan" target="_blank">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>
><br>
<br>
<br>
<br>
</div></div>--<br>
<div class="im">Gavin King<br>
<a href="mailto:gavin.king@gmail.com">gavin.king@gmail.com</a><br>
</div><div><div></div><div class="h5"><a href="http://in.relation.to/Bloggers/Gavin" target="_blank">http://in.relation.to/Bloggers/Gavin</a><br>
<a href="http://hibernate.org" target="_blank">http://hibernate.org</a><br>
<a href="http://seamframework.org" target="_blank">http://seamframework.org</a><br>
</div></div></blockquote></div><br><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'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>