On 8/30/05, Gary VanMatre <[EMAIL PROTECTED]> wrote: > > > This is a bug in Shale. I will post a bug to Bugzilla shortly. > > > > I assume they are talking about the RestoreViewPhase verses a decorator of > a handler calling createView on its original handler which would make it the > caller? I guess that I'm wondering if the ShaleViewHandler could explicitly > set the viewId on the returned UIViewRoot?
Sean was correct ... the Shale ViewHandler (or any other ViewHandler) should *not* set the viewId into the created UIViewRoot instance ... that should be done by the caller. I didn't look at our Clay or Tiles view handlers to make sure they don't suffer from the same problem, but I fixed ShaleViewHandler and the dialog navigation handler per Sean's patches. Gary > > > sean > > > > On 8/30/05, Sean Schofield <[EMAIL PROTECTED]> wrote: > > > I've run into a problem with the latest version of MyFaces. There was > > > a code change to the MyFaces JspViewHandler is no longer setting the > > > view id b/c of JSF spec issues. So ShaleViewHandler is returning null > > > in the following line of setupViewController: > > > > > > String viewName = viewControllerMapper.mapViewId(viewId); > > > > > > Is our interpretation of the spec correct here or is there a problem > > > with assumptions being made in Shale? > > > > > > sean > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
