On 10/13/05, Ryan Wynn <[EMAIL PROTECTED]> wrote: > I seem to be getting warning "No ViewControllerMapper has been configured > for this application". > > This started happening in the portlet environment, not in plain servlet > environment. > > First question, should I have to set up a view controller mapper instance > in the first place because shouldn't Shale pick the default if I don't > override? e.g org.apache.shale.view.impl.DefaultViewControllerMapper <snip/>
I believe the intent is to have it be picked up, but that happens in the ShaleApplicationFilter which might not be set up correctly for your portlet environment (whether you can set it up in depends on what environment you're using -- the portlet spec v1.0 doesn't say much about filters -- WebSphere Portal, IIRC, has some notion of portlet filters). > > Second question, I looked at the code for ShaleViewHandler. The > getViewControllerMapper method does the following: > > > context.getExternalContext().getApplicationMap().get(ShaleConstants.VIEW_MAPPER) > > Am I wrong or should this be doing something like > context.getApplication().getVariableResolver().resolveVariable(facesContext, > ShaleConstants.VIEW_MAPPER) > > That way I can override the view controller mapper in my faces-config.xml. > > Right now I am getting null back even though I define it in > faces-config.xml under application scope and I think it may be because it > is not going through the variable resolver. > <snap/> The ShaleViewHandler is merely retrieving what the ShaleApplicationFilter has instantiated as the ViewControllerMapper (and placed in the application map). -Rahul --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
