I've been following YAGNI principles about adding method to Request that shadow HttpServletRequest ... that is, waiting until there's a specific need. It's not just the couple of lines of Request/RequestImpl, but also the creation of the corresponding tests. Adding a request to JIRA is not inappropriate, and less likely to get misplaced than posting here.
On 2/15/07, Massimo Lusetti <[EMAIL PROTECTED]> wrote:
In a very custom page which is only returning a byte stream, no text/html output just binary, I need to have access to the IP value to being able to verify some conditions, so i wish to have access to this value through org.apache.tapestry.services.Request. I know this is a very untypical usage of a Tapestry page and this could open a debate on "where we stop" adding value from HttpServletRequest to the Request wrapper but maybe this value could be useful to some one else. For the record i decided to use a Tapestry page and not going directly with a servlet since i can access all the nifty features from Tapestry IoC which has saved me a lot of typing and coding. What do you think? Regards -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- Howard M. Lewis Ship TWD Consulting, Inc. Independent J2EE / Open-Source Java Consultant Creator and PMC Chair, Apache Tapestry Creator, Apache HiveMind Professional Tapestry training, mentoring, support and project work. http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
