Announcement Announcement Module
No announcement yet.
Setting the incorrect Context Path to include a JSP Page Title Module
Move Remove Collapse
Conversation Detail Module
  • Filter
  • Time
  • Show
Clear All
new posts

  • Setting the incorrect Context Path to include a JSP


    I am attempting to get the Spring Portlet Framework
    integrated with the Vignette Application Portal server (VAP) (7.1), running on Tomcat(4.1.27).

    I am able to run JSR 168 portlets on VAP running on Tomcat.
    Unfortunately, my success does not extend to Spring Portlets.

    It is the sample portlet "booksView" that I am attempting to get working.
    Although, I had to make changes to JSPs and taglibs etc in order to make it compatible with my environment.
    I've called this web-app : "sample".

    I have traced the thread of execution, and it appears the problem
    is in the setting of the context and context path.

    When the portal performs the ViewRendererServlet,
    it is able to determine the correct context path for the sample web application mapping:
    The servlet mapping for this is defined in the web.xml file.

    Then, it will attempt at (RequestDispatcher) "including" the "booksView.jsp"

    This is attempted by prepending the sample web-app's relative path with the portal's context root,
    rather than the sample web-app's context root.

    When it executes the RequestDispatcher's "include" method,
    The final request URI is "/portal/WEB-INF/books/booksView.jsp"
    When it should be "/sample/WEB-INF/books/booksView.jsp"

    And, because the wrong path is supplied, the JSP is not found.

    What should I do to ensure Tomcat's application dispatcher references the correct context and context path,
    after the ViewRenderServlet attenpts to include a JSP ?

    I have my web-app to use the "InternalResourceViewResolver".

    Note, I can get the sample web-app to work, if I insert the book's JSPs
    into the portal's WEB-INF directory.

    any help would be greatly appreciated.....


  • #2
    I believe this is actually a bug in VAP. See this posting: