Caldarale, Charles R wrote: > Since query information is normally unique to a request, I think the > above could be construed that the RequestDispatcher is cognizant of the > query string. If so, each RequestDispatcher would be associated with a > specific request.
I agree that the RD is cognizant of the query string but I don't see that this prevents the RD from being re-used. The RD merges its query string (specified on creation) with the query string of the request passed to the include/forward method. No reason it can't do this several times. > SRV.15.2.8 ServletContext, getRequestDispatcher(String): > "The resource can be dynamic or static." > > Since dynamic resources can come and go and their existence can be > dependent on specific requests, there is an implication that a > RequestDispatcher is associated with the request it has been created > for. I see where you are coming form here but this strikes me as an application issue. > "Send lawyers, guns, and money." (That's not in the spec, but perhaps > should be.) He he. Indeed! What does it for me is: a) that you can obtain an RD from the context; b) SRV.8.1 that states: "The method uses the path to look up a servlet ... wraps it with a RequestDispatcher object, and returns the resulting object." In my mind this aligns RDs more with servlets than requests. I plan to look at modifying the current RD code over the holiday. Mark --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
