That just seems to me like the opposite of what we are trying to achieve
with injection.
I would argue against HttpSession and request (I'm assuming ServletRequest)
because that is the point of FacesContext...to abstract that away somewhat.
But you still need FacesContext.
-Dan
On Tue, Nov 10, 2009 at 4:51 PM, Gavin King <gavin.king(a)gmail.com> wrote:
Call FacesContext.setCurrentInstance() :-)
On Tue, Nov 10, 2009 at 4:29 PM, Steven Boscarine
<steven.boscarine(a)childrens.harvard.edu> wrote:
>
> Gavin King wrote:
>>
>> I didn't put it in, since I figured it was hard to justify that this
>> is better than FacesContext.getCurrentInstance().
>>
>
> How would one unit test a class that has such a call?
>
>
>
--
Gavin King
gavin.king(a)gmail.com
http://in.relation.to/Bloggers/Gavin
http://hibernate.org
http://seamframework.org
--
Dan Allen
Senior Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://mojavelinux.com
http://mojavelinux.com/seaminaction
http://www.google.com/profiles/dan.j.allen