You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Mike La Budde <mi...@irista.com> on 2000/10/05 22:52:42 UTC
Correction To: context-relative paths are painfull
Please see interspersed comments.
At 10/05/2000 03:42 PM -0500, Mike La Budde wrote:
>OK, yes, I'm still wrestling with this issue.
>
>Here's a snippet from my struts actions configuration file:
>
> <!-- ========== Global Forward Definitions
> ============================== -->
> <global-forwards>
> <forward name="logon" path="/logon.jsp"/>
> <forward name="success" path="/pages/main/index.html"/>
> <forward name="error" path="/ErrorActionViewPage.do"/>
> </global-forwards>
>
> <!-- ========== Action Mapping Definitions
> ============================== -->
> <action-mappings>
>
> <!-- ============================ Error BEGIN
> ============================= -->
>
> <action path="/ErrorActionViewPage"
> type="com.irista.ui.web.fulfill.ErrorActionViewPage">
> <forward name="success" path="/pages/main/error.jsp"/>
> </action>
>
> <action path="/ErrorDtlActionViewPage"
> type="com.irista.ui.web.fulfill.ErrorDtlActionViewPage">
> <forward
> name="success" path="/pages/main/errorDetail.jsp"/>
> </action>
>
> <!-- ============================ Error END
> =============================== -->
>
>
>If an error occurs I'm getting to /pages/main/error.jsp (thru' the global
>error forward /ErrorActionViewPage.do). This error page has a "View
>Details" button on it. However, attempting to view the details hangs or
>gets a 404 (page not found) error. Looking at the console window shows
>that it has somehow lost its context and it thinks its in the ROOT.
>Changing the above forward path for the ErrorDtlActionViewPage to
>path="/mycontextName/pages/main/errorDetail.jsp" works!
Sorry. Wrong, this isn't what we changed. We changed the link in the
error.jsp page from /ErrorDtlActionViewPage.do to
/mycontextName/ErrorDtlActionViewPage.do and then it worked.... I'm still
just as confused, tho'. ;-)
>Ouch! I'm totally confused by this behavior. (Not to mention that my
>earlier confusion (dismay?) at having to specify all paths as fully
>qualified context relative in the first place hasn't been satisfactorily
>cleared up. Hell, I got confused just re-reading that last sentence!)
>
>Based on yesterday's exchanges between Craig & Colin I know I'm going to
>have even more fun when I get to the point where I'm configuring security
>for our apps! (Another opportunity...)
>
>TIA,
>
>Mike