/en/page1.xhtml Not Found in ExternalContext as a Resource

Oracle Community | sebaxtz1 | 6 years ago
  1. 0

    db:: 3.76::a problem about url filter of web dispatcher jm | 6 months ago /en/page1.xhtml Not Found in ExternalContext as a Resource
  2. 0

    filter bug in Glassfish 2.1.1. ?

    Oracle Community | 6 years ago | sebaxtz1 /en/page1.xhtml Not Found in ExternalContext as a Resource
  3. 0

    Icefaces and Spring Web Flow 2.0 Integration | 1 year ago /main Not Found in ExternalContext as a Resource
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Re:Icefaces and Spring Webflow 2.0.8 and Spring 3.0.0

    Icesoft | 7 years ago | polterghost /main Not Found in ExternalContext as a Resource
  6. 0

    When you directly access the IceFaces Portlet deployed in Web Space Server and click on a link within the portlet, it fails with the following exception: [#|2010-02-04T14:42:02.960+0000|INFO|sun-appserver2.1||_ThreadID=27;_ThreadName=httpSSLWorkerThread-8082-0;|2010-02-04 14:42:02,956 ERROR [httpSSLWorkerThread-8082-0] com.icesoft.faces.facelets.D2DFaceletViewHandler - Problem in renderResponse: /send-receive-updates Not Found in ExternalContext as a Resource /send-receive-updates Not Found in ExternalContext as a Resource at com.sun.facelets.impl.DefaultFaceletFactory.resolveURL( at com.sun.facelets.impl.DefaultFaceletFactory.getFacelet( at com.icesoft.faces.facelets.D2DFaceletViewHandler.renderResponse( at com.icesoft.faces.application.D2DViewHandler.renderView( at com.icesoft.faces.context.BridgeFacesContext$SwitchViewHandler.renderView( at com.sun.faces.lifecycle.RenderResponsePhase.execute( at com.sun.faces.lifecycle.LifecycleImpl.phase( at com.sun.faces.lifecycle.LifecycleImpl.render( at com.icesoft.faces.webapp.http.core.JsfLifecycleExecutor.apply( at com.icesoft.faces.context.View$2$1.respond( at com.icesoft.faces.webapp.http.servlet.ServletRequestResponse.respondWith( at com.icesoft.faces.context.View$2.serve( at com.icesoft.faces.context.View.servePage( at com.icesoft.faces.webapp.http.core.MultiViewServer.service( at com.icesoft.faces.webapp.http.common.ServerProxy.service( at com.icesoft.faces.webapp.http.servlet.MainSessionBoundServlet$4.service( at com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer.service( at com.icesoft.faces.webapp.http.servlet.BasicAdaptingServlet.service( at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service( at com.icesoft.faces.webapp.http.servlet.SessionDispatcher.service( at com.icesoft.faces.webapp.http.servlet.SessionVerifier.service( at com.icesoft.faces.webapp.http.servlet.PathDispatcher.service( at com.icesoft.faces.webapp.http.servlet.MainServlet.service( at javax.servlet.http.HttpServlet.service( Steps to reproduce: 1. Create IceFaces Portlet(eg:IceFacesPortletLinkTest) that has a commandLink and deploy it. 2. Add it on a public page of Web Space Server(eg: http://localhost:8080/web/guest/page1) 3. Click on the link in IceFaces Portlet, it works fine 4. Now close the browser. 5. Open the browser and access the page directly(i.e access http://localhost:8080/web/guest/page1) 6. Now when you click on the link in IceFaces Portlet, it throws an exception(as mentioned above). Cause: After debugging the sources, we found this was because of the way the pattern is matched. After step#5 above, if you view the page source, you see that the value of "sendReceiveUpdatesURI" is '/IceFacesPortletLinkTest/block/send-receive-updates;jsessionid=79bf8441f1e6cbc65be1555d53f7'. In com.icesoft.faces.webapp.http.common.standard.PathDispatcherServer, the value returned by the method request.getURI().getPath() is "/IceFacesPortletLinkTest/block/send-receive-updates;jsessionid=79bf8441f1e6cbc65be1555d53f7", but the pattern used to match is ".*block\/send\-receive\-updates$". As the URL ends with jsessionid, the match does not happen, resulting in the failure. The jsessionid is getting attached to the url because this is the first request from the server to the new browser session. We think that this can be fixed by modifying the Pattern.

    ICEsoft JIRA Issue Tracker | 7 years ago | Deepak Gothe /send-receive-updates Not Found in ExternalContext as a Resource

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis


      /en/page1.xhtml Not Found in ExternalContext as a Resource

      at com.sun.facelets.impl.DefaultFaceletFactory.resolveURL()
    2. Facelets
      1. com.sun.facelets.impl.DefaultFaceletFactory.resolveURL(
      2. com.sun.facelets.impl.DefaultFaceletFactory.getFacelet(
      2 frames
    3. com.icesoft.faces
      1. com.icesoft.faces.facelets.D2DFaceletViewHandler.renderResponse(
      2. com.icesoft.faces.application.D2DViewHandler.renderView(
      2 frames
    4. JSF
      1. com.sun.faces.lifecycle.RenderResponsePhase.execute(
      1 frame