I agree. This is one case where I&#39;m all for backwards compatibility! +1<br><br><div class="gmail_quote">On Mon, Feb 15, 2010 at 4:54 PM, Jason Lee <span dir="ltr">&lt;<a href="mailto:jason@steeplesoft.com">jason@steeplesoft.com</a>&gt;</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;"><div class="im">On 2/15/10 3:49 PM, Andy Schwartz wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
FWIW, my feeling is that, while returning null is a reasonable workaround, there is no way that our unit test is not the only code out there that is returning empty action outcomes and expecting to stay on the same page. I would like to see this behavior preserved not so that we can revert our unit test to its previous behavior (I am fine with our fix), but because the current behavior may break other users as they upgrade to JSF2.<br>

<br>
Thoughts?<br>
</blockquote></div>
I know in the apps I&#39;ve worked on whether I return an empty String or null depends on the mood I&#39;m in. :) �I think we should clarify the spec to preserve the 1.2 behavior.<br><font color="#888888">
<br>
-- <br>
Jason Lee, SCJP<br>
President, Oklahoma City Java Users Group<br>
Senior Java Developer, Sun Microsystems<br>
<a href="http://blogs.steeplesoft.com" target="_blank">http://blogs.steeplesoft.com</a><br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Lincoln Baxter, III<br><a href="http://ocpsoft.com">http://ocpsoft.com</a><br><a href="http://scrumshark.com">http://scrumshark.com</a><br>&quot;Keep it Simple&quot;<br>