|
From: SourceForge.net <no...@so...> - 2005-06-15 16:27:33
|
Bugs item #1121596, was opened at 2005-02-12 20:04 Message generated for change (Comment added) made by sgarlatm You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=700930&aid=1121596&group_id=124910 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None >Status: Closed Resolution: None Priority: 1 Submitted By: Matt Sgarlata (sgarlatm) Assigned to: Nobody/Anonymous (nobody) Summary: Have web reflectors expose additional implicit properties? Initial Comment: Consider fixing the web reflectors so that they expose implicit properties like requestScope, sessionScope, etc (following the JSTL). Along this same line of thinking, should we expose all the JavaBeans properties of an HTTP request? If so, how do we deal with collisions between the JavaBeans properties and HTTP request attributes? Should this be a JavaBean property of the converter? ---------------------------------------------------------------------- >Comment By: Matt Sgarlata (sgarlatm) Date: 2005-06-15 12:27 Message: Logged In: YES user_id=1161666 No, if this type of thing is added it will be added to the Context implementations instead of to the reflectors. There are already enough issues with there being two reflectors for request parameters ;) ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=700930&aid=1121596&group_id=124910 |
