Re: another commandLink problem
If the returned string for the action is null or unknown to the navigation manager, it'll show the same page again. Also, if the commandLink isn't rendered either before or after the request, it'll return the same page. Same thing if the link is inside a UIData component and the UIData model isn't preserved across requests (t:saveState on request-scoped data). On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. Anyone know what is causing this, how to fix it? Shawn This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ***
RE: another commandLink problem
Well I'd say it's definitely know to the navigation handler because it finds the page the second time I click on the same link. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem If the returned string for the action is null or unknown to the navigation manager, it'll show the same page again. Also, if the commandLink isn't rendered either before or after the request, it'll return the same page. Same thing if the link is inside a UIData component and the UIData model isn't preserved across requests (t:saveState on request-scoped data). On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. Anyone know what is causing this, how to fix it? Shawn This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. *** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
Re: another commandLink problem
Right, but the second time you've clicked on the link, the page has been redrawn, the component tree updated, and the request map reset, etc, so that doesn't really eliminate any possibilities. :) If you're using a hardcoded action literal string, then yes, you can eliminate the navigation manager cause. If you're not using rendered in the link or any of its ancestors, you can eliminate that. If there's a UIData component in the ancestors, that's the likely cause -- you need to preserve the backing data model between requests. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: Well I'd say it's definitely know to the navigation handler because it finds the page the second time I click on the same link. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem If the returned string for the action is null or unknown to the navigation manager, it'll show the same page again. Also, if the commandLink isn't rendered either before or after the request, it'll return the same page. Same thing if the link is inside a UIData component and the UIData model isn't preserved across requests (t:saveState on request-scoped data). On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. Anyone know what is causing this, how to fix it? Shawn This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. *** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
RE: another commandLink problem
I don't get what the problem is then? Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:27 PM To: MyFaces Discussion Subject: Re: another commandLink problem Right, but the second time you've clicked on the link, the page has been redrawn, the component tree updated, and the request map reset, etc, so that doesn't really eliminate any possibilities. :) If you're using a hardcoded action literal string, then yes, you can eliminate the navigation manager cause. If you're not using rendered in the link or any of its ancestors, you can eliminate that. If there's a UIData component in the ancestors, that's the likely cause -- you need to preserve the backing data model between requests. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: Well I'd say it's definitely know to the navigation handler because it finds the page the second time I click on the same link. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem If the returned string for the action is null or unknown to the navigation manager, it'll show the same page again. Also, if the commandLink isn't rendered either before or after the request, it'll return the same page. Same thing if the link is inside a UIData component and the UIData model isn't preserved across requests (t:saveState on request-scoped data). On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. Anyone know what is causing this, how to fix it? Shawn This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. *** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
Re: another commandLink problem
Can you post your jsp or facelets page code? It's not really possible to give anything beyond the vague answers below without more specific information. It'd probably also be helpful to post the faces-config information for any managed beans being used. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I don't get what the problem is then? Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:27 PM To: MyFaces Discussion Subject: Re: another commandLink problem Right, but the second time you've clicked on the link, the page has been redrawn, the component tree updated, and the request map reset, etc, so that doesn't really eliminate any possibilities. :) If you're using a hardcoded action literal string, then yes, you can eliminate the navigation manager cause. If you're not using rendered in the link or any of its ancestors, you can eliminate that. If there's a UIData component in the ancestors, that's the likely cause -- you need to preserve the backing data model between requests. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: Well I'd say it's definitely know to the navigation handler because it finds the page the second time I click on the same link. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem If the returned string for the action is null or unknown to the navigation manager, it'll show the same page again. Also, if the commandLink isn't rendered either before or after the request, it'll return the same page. Same thing if the link is inside a UIData component and the UIData model isn't preserved across requests (t:saveState on request-scoped data). On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. Anyone know what is causing this, how to fix it? Shawn This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. *** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
RE: another commandLink problem
navigation-rule from-view-id/context07/summary.jsp/from-view-id navigation-case from-outcomecollege/from-outcome to-view-id/context07/college.jsp/to-view-id /navigation-case ... rest of navigation-cases /navigation-rule if I type in /context07/college.faces in the url the college page comes right up. However the h:commandLink action=college/ on the summary page I have to click on it and then click on it again. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:39 PM To: MyFaces Discussion Subject: Re: another commandLink problem Can you post your jsp or facelets page code? It's not really possible to give anything beyond the vague answers below without more specific information. It'd probably also be helpful to post the faces-config information for any managed beans being used. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I don't get what the problem is then? Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:27 PM To: MyFaces Discussion Subject: Re: another commandLink problem Right, but the second time you've clicked on the link, the page has been redrawn, the component tree updated, and the request map reset, etc, so that doesn't really eliminate any possibilities. :) If you're using a hardcoded action literal string, then yes, you can eliminate the navigation manager cause. If you're not using rendered in the link or any of its ancestors, you can eliminate that. If there's a UIData component in the ancestors, that's the likely cause -- you need to preserve the backing data model between requests. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: Well I'd say it's definitely know to the navigation handler because it finds the page the second time I click on the same link. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem If the returned string for the action is null or unknown to the navigation manager, it'll show the same page again. Also, if the commandLink isn't rendered either before or after the request, it'll return the same page. Same thing if the link is inside a UIData component and the UIData model isn't preserved across requests (t:saveState on request-scoped data). On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. Anyone know what is causing this, how to fix it? Shawn This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. *** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
Re: another commandLink problem
From: "Garner, Shawn" [EMAIL PROTECTED] I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. This is common behavior in MyFaces when you use the brower back button to a dirty page and repost it. I believe it has to do with how the component tree's state is saved. I suspect that myfaces only caches a single page. So, navigation to a new page overrides the cached state of the old. The double post is needed because the state manager can't resort the view and just skips to the render phase. The RI behaves differently here. Anyone know what is causing this, how to fix it? Try turning on client side state saving. You do this in your web deployment descriptor. context-param param-namejavax.faces.STATE_SAVING_METHOD/param-name param-valueclient/param-value /context-param Shawn Gary
Re: another commandLink problem
Right. We know the navigation rules are correct which is why I didn't ask for them. The jsp code and possibly the managed bean definitions are what we need to see. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: navigation-rule from-view-id/context07/summary.jsp/from-view-id navigation-case from-outcomecollege/from-outcome to-view-id/context07/college.jsp/to-view-id /navigation-case ... rest of navigation-cases /navigation-rule if I type in /context07/college.faces in the url the college page comes right up. However the h:commandLink action=college/ on the summary page I have to click on it and then click on it again. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:39 PM To: MyFaces Discussion Subject: Re: another commandLink problem Can you post your jsp or facelets page code? It's not really possible to give anything beyond the vague answers below without more specific information. It'd probably also be helpful to post the faces-config information for any managed beans being used. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I don't get what the problem is then? Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:27 PM To: MyFaces Discussion Subject: Re: another commandLink problem Right, but the second time you've clicked on the link, the page has been redrawn, the component tree updated, and the request map reset, etc, so that doesn't really eliminate any possibilities. :) If you're using a hardcoded action literal string, then yes, you can eliminate the navigation manager cause. If you're not using rendered in the link or any of its ancestors, you can eliminate that. If there's a UIData component in the ancestors, that's the likely cause -- you need to preserve the backing data model between requests. On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: Well I'd say it's definitely know to the navigation handler because it finds the page the second time I click on the same link. Shawn -Original Message- From: Mike Kienenberger [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem If the returned string for the action is null or unknown to the navigation manager, it'll show the same page again. Also, if the commandLink isn't rendered either before or after the request, it'll return the same page. Same thing if the link is inside a UIData component and the UIData model isn't preserved across requests (t:saveState on request-scoped data). On 1/17/06, Garner, Shawn [EMAIL PROTECTED] wrote: I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. Anyone know what is causing this, how to fix it? Shawn This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. *** This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
RE: another commandLink problem
I tried client and now it blows up on every link on pages that use to work. I don't use the back button. I just use the same url from a new browser window after I restart the server. Shawn From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 2:55 PM To: MyFaces Discussion Subject: Re: another commandLink problem From: Garner, Shawn [EMAIL PROTECTED] I've noticed my commandLinks don't go to the page the first time. It seems to reload the page and then if I click on it again it goes to the next view. This is common behavior in MyFaces when you use the brower back button to a dirty page and repost it. I believe it has to do with how the component tree's state is saved. I suspect that myfaces only caches a single page. So, navigation to a new page overrides the cached state of the old. The double post is needed because the state manager can't resort the view and just skips to the render phase. The RI behaves differently here. Anyone know what is causing this, how to fix it? Try turning on client side state saving. You do this in your web deployment descriptor. context-param param-namejavax.faces.STATE_SAVING_METHOD/param-name param-valueclient/param-value /context-param Shawn Gary This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ***
RE: another commandLink problem
From: "Garner, Shawn" [EMAIL PROTECTED] I tried client and now it blows up on every link on pages that use to work. I don't use the back button. I just use the same url from a new browser window after I restart the server. What does the exception say? Shawn Gary
Re: another commandLink problem
I tried client and now it blows up on every link on pages that use to work. Stacktrace? Meaningful description? Dennis Byrne
RE: another commandLink problem
I don't think it's meaningful: javax.faces.FacesException: Unhandled exception thrown from /context07/personal.jsp:16 at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:421) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHand lerImpl.java:234) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) Caused by: jrun.jsp.runtime.UncaughtPageException: Unhandled exception thrown from /context07/personal.jsp:16 at jrun.jsp.runtime.Utils.handleException(Utils.java:57) at jrun.jsp.runtime.JRunPageContext.handlePageException(JRunPageContext.java:39 0) at jrun__context07__personal_2ejsp1f._jspService(jrun__context07__ personal2ejsp1f.java:1684) at jrun.jsp.runtime.HttpJSPServlet.service(HttpJSPServlet.java:43) at jrun.jsp.JSPServlet.service(JSPServlet.java:119) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invokeNext(JRunRequestDispatcher.java:534 ) at jrun.servlet.JRunRequestDispatcher.forwardInvoke(JRunRequestDispatcher.java: 503) at jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:177) at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:415) ... 10 more javax.servlet.ServletException: Unhandled exception thrown from /context07/personal.jsp:16 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:121) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) -Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 3:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem I tried client and now it blows up on every link on pages that use to work. Stacktrace? Meaningful description? Dennis Byrne This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
RE: another commandLink problem
That's weird. Itlooks like your page doesn't have a view root defined. Do you have the f:view /f:viewtag in your jsp? -- Original message -- From: "Garner, Shawn" [EMAIL PROTECTED] I don't think it's meaningful: javax.faces.FacesException: Unhandled exception thrown from /context07/personal.jsp:16 at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:421) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHand lerImpl.java:234) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequest Dispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) Caused by: jrun.jsp.runtime.UncaughtPageException: Unhandled exception thrown from /context07/personal.jsp:16 at jrun.jsp.runtime.Utils.handleException(Utils.java:57) at jrun.jsp.runtime.JRunPageContext.handlePageException(JRunPageContext.java:39 0) at jrun__context07__personal_2ejsp1f._jspService(jrun__context07__ personal2ejsp1f.java:1684) at jrun.jsp.runtime.HttpJSPServlet.service(HttpJSPServlet.java:43) at jrun.jsp.JSPServlet.service(JSPServlet.java:119) at jrun.servlet.ServletInvoke r.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invokeNext(JRunRequestDispatcher.java:534 ) at jrun.servlet.JRunRequestDispatcher.forwardInvoke(JRunRequestDispatcher.java: 503) at jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:177) at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:415) ... 10 more javax.servlet.ServletException: Unhandled exception thrown from /context07/personal.jsp:16 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:121) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunR equestDispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)-Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 3:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem I tried client and now it blows up on every link on pages that use to work. Stacktrace? Meaningful description? Dennis Byrne This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
RE: another commandLink problem
Sorry, I was off a few lines. What is your faces servlet mapping? Is it mapped to *.faces. I'mguessing that that view handler thinks this is an external mapping that's why it's doing the dispatchversus swapping out the view. Are you using /context07/personal.jsp from your browser or /context07/personal.faces? Gary -- Original message -- From: "Garner, Shawn" [EMAIL PROTECTED] I don't think it's meaningful: javax.faces.FacesException: Unhandled exception thrown from /context07/personal.jsp:16 at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:421) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHand lerImpl.java:234) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequest Dispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) Caused by: jrun.jsp.runtime.UncaughtPageException: Unhandled exception thrown from /context07/personal.jsp:16 at jrun.jsp.runtime.Utils.handleException(Utils.java:57) at jrun.jsp.runtime.JRunPageContext.handlePageException(JRunPageContext.java:39 0) at jrun__context07__personal_2ejsp1f._jspService(jrun__context07__ personal2ejsp1f.java:1684) at jrun.jsp.runtime.HttpJSPServlet.service(HttpJSPServlet.java:43) at jrun.jsp.JSPServlet.service(JSPServlet.java:119) at jrun.servlet.ServletInvoke r.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invokeNext(JRunRequestDispatcher.java:534 ) at jrun.servlet.JRunRequestDispatcher.forwardInvoke(JRunRequestDispatcher.java: 503) at jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:177) at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:415) ... 10 more javax.servlet.ServletException: Unhandled exception thrown from /context07/personal.jsp:16 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:121) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunR equestDispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)-Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 3:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem I tried client and now it blows up on every link on pages that use to work. Stacktrace? Meaningful description? Dennis Byrne This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network.
RE: another commandLink problem
*.faces From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 4:18 PM To: MyFaces Discussion Subject: RE: another commandLink problem Sorry, I was off a few lines. What is your faces servlet mapping? Is it mapped to *.faces. I'mguessing that that view handler thinks this is an external mapping that's why it's doing the dispatchversus swapping out the view. Are you using /context07/personal.jsp from your browser or /context07/personal.faces? Gary -- Original message -- From: Garner, Shawn [EMAIL PROTECTED] I don't think it's meaningful: javax.faces.FacesException: Unhandled exception thrown from /context07/personal.jsp:16 at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:421) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHand lerImpl.java:234) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequest Dispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) Caused by: jrun.jsp.runtime.UncaughtPageException: Unhandled exception thrown from /context07/personal.jsp:16 at jrun.jsp.runtime.Utils.handleException(Utils.java:57) at jrun.jsp.runtime.JRunPageContext.handlePageException(JRunPageContext.java:39 0) at jrun__context07__personal_2ejsp1f._jspService(jrun__context07__ personal2ejsp1f.java:1684) at jrun.jsp.runtime.HttpJSPServlet.service(HttpJSPServlet.java:43) at jrun.jsp.JSPServlet.service(JSPServlet.java:119) at jrun.servlet.ServletInvoke r.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invokeNext(JRunRequestDispatcher.java:534 ) at jrun.servlet.JRunRequestDispatcher.forwardInvoke(JRunRequestDispatcher.java: 503) at jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:177) at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:415) ... 10 more javax.servlet.ServletException: Unhandled exception thrown from /context07/personal.jsp:16 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:121) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunR equestDispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) -Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 3:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem I tried client and now it blows up on every link on pages that use to work. Stacktrace? Meaningful description? Dennis Byrne This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ***
RE: another commandLink problem
From the stack it doesn't look like your are using Shale or Clay so you can remove all but the *.faces mapping.I don'tthink that's yourproblem. I can't see what is going on here. I'm afraid that I'm just giving you bad information. Gary -- Original message -- From: "Garner, Shawn" [EMAIL PROTECTED] Actually: servlet-mapping servlet-namefaces& lt;/servlet-name url-pattern*.faces /url-pattern /servlet-mapping !-- JavaServer Faces Servlet Mapping for Clay HTML Full View -- servlet-mapping servlet-namefaces& lt;/servlet-name url-pattern*.html& lt;/url-pattern /servlet-mapping !-- JavaServer Faces Servlet Mapping for Clay XML Full View -- servlet-mapping servlet-namefaces& lt;/servlet-name url-pattern*.xml t;/url-pattern /servlet-mapping From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 4:18 PMTo: MyFaces DiscussionSubject: RE: another commandLink problem Sorry, I was off a few lines. What is your faces servlet mapping? Is it mapped to *.faces. I'mguessing that that view handler thinks this is an external mapping that's why it's doing the dispatchversus swapping out the view. Are you using /context07/personal.jsp from your browser or /context07/personal.faces? Gary -- Original message -- From: "Garner, Shawn" [EMAIL PROTECTED] I don't think it's meaningful: javax.faces.FacesException: Unhandled exception thrown from /context07/personal.jsp:16 at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:421) at org.apache.myfaces.application.jsp.JspViewHandlerImpl.renderView(JspViewHand lerImpl.java:234) at org.apache.myfaces.lifecycle.LifecycleImpl.render(LifecycleImpl.java:352) at javax.faces.webapp.FacesServlet.service(FacesServlet.java:107) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequest Di spatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66) Caused by: jrun.jsp.runtime.UncaughtPageException: Unhandled exception thrown from /context07/personal.jsp:16 at jrun.jsp.runtime.Utils.handleException(Utils.java:57) at jrun.jsp.runtime.JRunPageContext.handlePageException(JRunPageContext.java:39 0) at jrun__context07__personal_2ejsp1f._jspService(jrun__context07__ personal2ejsp1f.java:1684) at jrun.jsp.runtime.HttpJSPServlet.service(HttpJSPServlet.java:43) at jrun.jsp.JSPServlet.service(JSPServlet.java:119) at jrun.servlet.ServletInvoke r .invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunRequestDispatcher.invokeNext(JRunRequestDispatcher.java:534 ) at jrun.servlet.JRunRequestDispatcher.forwardInvoke(JRunRequestDispatcher.java: 503) at jrun.servlet.JRunRequestDispatcher.forward(JRunRequestDispatcher.java:177) at org.apache.myfaces.context.servlet.ServletExternalContextImpl.dispatch(Servl etExternalContextImpl.java:415) ... 10 more javax.servlet.ServletException: Unhandled exception thrown from /context07/personal.jsp:16 at javax.faces.webapp.FacesServlet.service(FacesServlet.java:121) at jrun.servlet.ServletInvoker.invoke(ServletInvoker.java:91) at jrun.servlet.JRunInvokerChain.invokeNext(JRunInvokerChain.java:42) at jrun.servlet.JRunR equestDispatcher.invoke(JRunRequestDispatcher.java:259) at jrun.servlet.ServletEngineService.dispatch(ServletEngineService.java:541) at jrun.servlet.http.WebService.invokeRunnable(WebService.java:172) at jrunx.scheduler.ThreadPool$ThreadThrottle.invokeRunnable(ThreadPool.java:428 ) at jrunx.scheduler.WorkerThread.run(WorkerThread.java:66)-Original Message- From: Dennis Byrne [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 17, 2006 3:14 PM To: MyFaces Discussion Subject: Re: another commandLink problem I tried client and now it blows up on every link on pages that use to work. Stacktrace? Meaningful description? Dennis Byrne This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. This email may contain confidential material. If you were not an intended recipient, Please notify the sender and delete all copies. We may monitor email to and from our network. ***
