Yeah I was using the google link as just an example for an external context. I took your advice and tried the handleNavigation. I get the same exact result as my previous attempts. More and more I am convinced this is a bug. I will add this as a comment to my JIRA issue.
-----Original Message----- From: William Hoover [mailto:[EMAIL PROTECTED] Sent: Wednesday, April 04, 2007 4:17 AM To: [email protected] Subject: RE: Dynamic Navigation Justin, I know this will not work for the google link, but in your previous message (and Jira issue) you attempt to set an internal url. If the url has a navigation rule you can use: FacesContext.getCurrentInstance().getApplication().getNavigationHandler().ha ndleNavigation(FacesContext.getCurrentInstance(), currentActionMethod, redirectActionMethod); -----Original Message----- From: Justin Mckay [mailto:[EMAIL PROTECTED] Sent: Tuesday, April 03, 2007 5:04 PM To: [email protected] Subject: Re: Dynamic Navigation Well I tried to just go the external context route and low and behold, I get the same behavior. //Redirect Option FacesContext context = FacesContext.getCurrentInstance(); HttpServletResponse response = (HttpServletResponse)context.getExternalContext().getResponse(); response.sendRedirect("http://www.google.com";); //Dispatch Option FacesContext context = FacesContext.getCurrentInstance(); context.getExternalContext().dispatch("http://www.google.com";); So I opened up an issue on JIRA as this is a bit of a show stopper for us L http://issues.apache.org/jira/browse/ADFFACES-434 Justin McKay Java Developer FAMIS Software, Inc. [EMAIL PROTECTED] (949) 553-6564 telephone (949) 553-6559 fax http://www.famis.com
