On Fri, 22 Nov 2002, Nelson, Laird wrote:
> [snip]
> > There is not going to be a useful workaround for this -- it's
> > fundamental
> > to the nature of the architecture.
>
> OK. So not even an extra optional attribute on the form tag somewhere ("Use
> servletPath X instead of servletPath Y"), bearing in mind the limitations of
> our current reporting requirements? Is my company unique in trying to do
> things this way?
>
I suppose there actually is one way to influence the URLs to behave more
like what reporting mechanisms would expect - use redirects instead of
forwards. The costs of this are very high (cannot use request attributes
to forward information to the view, and the time required for the extra
round trip to the client), but you'd then have the JSP page URL, instead
of the action URL, in your access logs.
Your company is probably not unique in misunderstanding this -- but using
the request URLs in a Struts-based app for reporting activity would be
like using an irrelevant benchmark and believing that it told you anything
useful about how *your* app will perform. You are just going to get
misled.
If you have folks willing to be convinced, it would not take a lot of
effort to create a very simple little Struts app that had a single Action,
which could return an ActionForward for any JSP page within the app. Run
this app, and select each of the JSP pages in turn. Then, look at the
access log and see that the requested URL was the same in every case.
Then ask "so why do you care so much about URLs?" :-)
> Thanks for your time and help.
>
> Laird
Craig
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
