I agree. This is one case where I'm all for backwards compatibility! +1
On Mon, Feb 15, 2010 at 4:54 PM, Jason Lee <jason(a)steeplesoft.com> wrote:
On 2/15/10 3:49 PM, Andy Schwartz wrote:
> 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.
>
> Thoughts?
>
I know in the apps I've worked on whether I return an empty String or null
depends on the mood I'm in. :) I think we should clarify the spec to
preserve the 1.2 behavior.
--
Jason Lee, SCJP
President, Oklahoma City Java Users Group
Senior Java Developer, Sun Microsystems
http://blogs.steeplesoft.com