Hi Matthias, I'm not an expert in the inner workings of JSF, views and navigation.
But here is what works for me. I never understood the sense of the xml navigation rules, and because we have a very large application with many pages, we were fed up typing in the navigation rules, and forgetting them from time to time. Thus, I took the myfaces implementation of the navigation handler, threw out all the xml navigation rule stuff, and used it as a custom navigation handler, that moves forward without looking for a rule. Essentially the navigation handler does the following things. Is is a redirect? If yes do a redirect via the external context. If no, call viewhandler create view, set the view id, call faces context set view root, and then render response. Long text, short message: try doing your own navigation handler. It's simple, and we were very happy with that, because we got a lot more control. Regards Frank Felix -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, January 30, 2006 2:50 AM To: Users MyFaces Subject: Custom ViewHandler - problem with navigation Hi! I'm implementing a custom view handler and encounter problems with the navigation. The view handler is responsible for handling pure code-level Java views and delegates the rendering of JSP pages to the default view handler. Because of the Java views, I don't have any files to specify in the faces-config.xml navigation rules. When I use an outcome for a Java view, the navigation handler says that it cannot find a matching navigation case, and stays on the current view: outcome=ParticipationView no matching navigation-case found, staying on current ViewRoot Does anybody of you know how to handle that? Regards, Matthias
