I know that works. My main concern was "does tomcat internally construct a new request". Because then I wouldn't be getting my wrapped request in the included page. But it appears to pass along the original request object (whatever it is).
> -----Original Message----- > From: Yan Lin [mailto:[EMAIL PROTECTED] > Sent: Wednesday, April 07, 2004 12:10 AM > To: Tomcat Users List > Subject: Re: Wrapping Requests and jsp:include > > > Hi, I think that's the correct behaviour for > <jsp:include> action. The request is shared among all > the included pages. If you are still in doubt, you > can do a simple test by setting a param in your > request for you main jsp file, then try to retrieve it > in your included jsp file. > > Hope this helps:). > > -Yan > > --- Mike Curwen <[EMAIL PROTECTED]> wrote: > > Hello, > > > > I'm just wanting to check if something is > > "consistent with Spec". I've > > tested code that performs the following, in tomcat > > 4.1.29, and it 'works > > as expected'. So I'm curious if this is a > > 'guaranteed' behaviour across > > all containers, or if this is one of those fuzzy > > areas, and it just > > happily works in Tomcat. > > > > I am using com.oreilly.servlet to upload files and > > I'm using them > > through a file upload filter and > > MultipartRequestWrapper class > > (borrowing heavily from those available in cos). > > > > in process.jsp: > > ------------------------------------------ > > <% > > MultipartRequestWrapper multi = > > (MultipartRequestWrapper) request; > > filename = multi.getFilesystemName("image_1"); > > logger.debug("filename: " + filename); > > %> > > > > <jsp:include page="someOtherJsp.jsp" /> > > ------------------------------------------ > > > > in someOtherJsp.jsp: > > ------------------------------------------ > > <% > > MultipartRequestWrapper multi = > > (MultipartRequestWrapper) request; > > filename = multi.getFilesystemName("image_1"); > > logger.debug("filename: " + filename); > > %> > > > > > > In my log4j logs: > > DEBUG com.gbim.web.FileUploadFilter - [wrapping > > request] > > DEBUG booster/process.jsp - [filename: > > separator.gif] > > DEBUG booster/someOtherJsp.jsp - [filename: > > separator.gif] > > > > > > So: I can access the request again, in the included > > file, as a > > MultiPartRequestWrapper. So when Tomcat, the > > container, makes its > > internal jsp:include request, it passes along the > > *existing* request, > > wrapped and everything, as is. I seemed to recall > > some conversation > > about facades getting in the way, but this has been > > taken care of since > > ? Or was I dreaming? I've googled for this (probably > > imagined) > > conversation, and can't find it. > > > > > > ----------------------------------------------- > > mike curwen > > intermediate programmer > > globally boundless > > > > 204 885-7733 ext 229 > > www.globallyboundless.com > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: > > [EMAIL PROTECTED] > > > > > __________________________________ > Do you Yahoo!? > Yahoo! Small Business $15K Web Design Giveaway > http://promotions.yahoo.com/design_giveaway/ > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
