Bug 4920

Summary: Changes to request taglib to allow store data on pagecontext and not only as Writer output
Product: Taglibs Reporter: Vicente Salvador <vicentesalvador>
Component: Request TaglibAssignee: Tomcat Developers Mailing List <dev>
Status: CLOSED WONTFIX    
Severity: normal    
Priority: P3    
Version: 1.0   
Target Milestone: ---   
Hardware: All   
OS: other   
Attachments: Zip file containing entire patches files
ZIP with Better patched files allowing JSP Java variable creation. Is anybody out there????

Description Vicente Salvador 2001-11-16 05:27:05 UTC
I've changed the request tablibs to allow store the request data into the 
pagecontext as other tags like dbtags do!!

I've not access to CVS, so I attach the files for your consideration!

Files attaches afterwards:

jakarta-taglibs\request\src\org\apache\taglibs\request\HeaderTag.java
jakarta-taglibs\request\src\org\apache\taglibs\request\CookieTag.java
jakarta-taglibs\request\src\org\apache\taglibs\request\ParameterTag.java
jakarta-taglibs\request\src\org\apache\taglibs\request\AttributeTag.java
jakarta-taglibs\request\xml\request.xml
Comment 1 Vicente Salvador 2001-11-16 05:31:59 UTC
Created attachment 798 [details]
Zip file containing entire patches files
Comment 2 Vicente Salvador 2001-11-22 10:08:40 UTC
Created attachment 817 [details]
ZIP with Better patched files allowing JSP Java variable creation. Is anybody out there????
Comment 3 Glenn Nielsen 2002-04-04 19:25:34 UTC
Saving request scope data as page or request scope makes no sense.  The data is
already available in the request.  Saving the request scope data as 
session or application might be useful, but it can be accomplished using the
session or application taglibs.

<sess:setAttribute name="foo"><req:parameter name="foo"/></sess:setAttribute>

Thanks for sending the patches, but I don't think they are needed.

Besides, the new JSP Standard Taglib is the way to go in the future.