I'd like to see log output as well; I added a comment to the issue.
___
Kito D. Mann | @kito99 | Author, JSF in Action
Virtua, Inc. |
http://www.virtua.com | JSF/Java EE training and consulting
http://www.JSFCentral.com - JavaServer Faces FAQ, news, and info |
@jsfcentral
+1 203-998-0403
* JSF in Action Public Course - NYC - April 2-4:
http://skillsmatter.com/course/java-jee/jsf-and-ajax
* Listen to the Enterprise Java Newscast: *
http://blogs.jsfcentral.com/JSFNewscast/
*
* JSFCentral Interviews Podcast:
http://www.jsfcentral.com/resources/jsfcentralpodcasts/
* Sign up for the JSFCentral Newsletter:
http://oi.vresp.com/?fid=ac048d0e17
On Wed, Feb 27, 2013 at 4:58 PM, Edward Burns <edward.burns_at_oracle.com>wrote:
> >>>>> On Wed, 27 Feb 2013 09:07:43 -0500, Kito Mann <kito.mann_at_virtua.com>
> said:
>
> KM> +1 in general. With respect to @ViewScope, I think the spec should
> require
> KM> a warning (I would prefer that it fail, actually.).
>
> We'll stick with a FacesMessage warning in the page.
>
> I just added a comment to the issue about this.
>
> KM> Basically we're saying
> KM> @ViewScope is incompatible with <f:view transient="true">, so why
> allow it
> KM> at all? Silently changing the behavior is going to really annoy people
> --
> KM> JSF does that enough :-).
>
> Based on preliminary discussion between Manfred and Hanspeter, it seems
> possible we can make @ViewScoped work with <f:view transient="true">,
> but the work is too risky for this late stage.
>
> Therefore, I'd rather stick with the warning now and remove the warning
> than simply disable it.
>
> I've filed JAVASERVERFACES-2761 to track this warning message, and
> Manfred has agreed to implement it.
>
> Ed
>
> --
>