Hi Leo, all!
After setting up 2 parallel debugging systems with an internal released
2.0.2-tiss-1 (from ~3 weeks before 2.0.2 went final) and the latest trunk, I
figured that the problem is in restoring the old viewParams from the ViewRoot
ViewMetadata #46
UIComponent metadataFacet = root.getFacet
(UIViewRoot.METADATA_FACET_NAME);
returns null in 2.0.3, whereas I got the correctly filled metadataFacet back in
2.0.2 (containing my UIViewParameter as children).
LieGrue,
strub
--- On Thu, 12/16/10, Leonardo Uribe <[email protected]> wrote:
From: Leonardo Uribe <[email protected]>
Subject: Re: problems with f:viewParam in myfaces-2.0.3
To: "MyFaces Development" <[email protected]>
Date: Thursday, December 16, 2010, 11:27 PM
Hi Mark
I think the change you are looking for is MYFACES-2985 Viewscoped bean does not
get destroyed when navigating with faces-redirect to a non-jsf-page.
regards,
Leonardo Uribe
2010/12/16 Mark Struberg <[email protected]>
oki, a bit more information: this happens with @ViewScoped beans (which use the
JSF ViewMap). Maybe the ViewMap gets cleaned too early in the
NavigationHandlerImpl?
LieGrue,
strub
--- On Thu, 12/16/10, Mark Struberg <[email protected]> wrote:
> From: Mark Struberg <[email protected]>
> Subject: problems with f:viewParam in myfaces-2.0.3
> To: [email protected]
> Date: Thursday, December 16, 2010, 8:41 PM
> hi!
>
> I experience a problem with f:viewParam if
> "destinationPage.xhtml?faces-redirect=true&includeViewParams=true"
>
> gets returned in an action.
>
> Die anything in this area got changed lately?
> Would make it easier for me to dig into the problem...
>
> LieGrue,
> strub
>
>
>
>
