DO NOT REPLY [Bug 45065] RequestDispatcher restricts access to ApplicationHttpRequest

2008-05-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45065 Paul Copeland <[EMAIL PROTECTED]> changed: What|Removed |Added CC||[EMAIL PROTECTE

DO NOT REPLY [Bug 45065] RequestDispatcher restricts access to ApplicationHttpRequest

2008-05-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45065 --- Comment #4 from Paul Copeland <[EMAIL PROTECTED]> 2008-05-27 11:42:25 PST --- (In reply to comment #3) The point of the question about forwarding to another context is that the class loader used to load the forwarded request wrappe

DO NOT REPLY [Bug 45065] RequestDispatcher restricts access to ApplicationHttpRequest

2008-05-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45065 --- Comment #5 from Mark Thomas <[EMAIL PROTECTED]> 2008-05-27 13:09:59 PST --- It's amazing what a night's sleep does for you. The explanation is simple and obvious - I should have seen it earlier. o.a.c.connector.RequestFacade is pub

DO NOT REPLY [Bug 45065] RequestDispatcher restricts access to ApplicationHttpRequest

2008-05-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45065 --- Comment #6 from Paul Copeland <[EMAIL PROTECTED]> 2008-05-27 14:00:41 PST --- (In reply to comment #5) Um will it is getting interesting. Are you saying the Request interface is implemented with a non-public method? Are you sure

DO NOT REPLY [Bug 45065] RequestDispatcher restricts access to ApplicationHttpRequest

2008-05-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45065 --- Comment #7 from Mark Thomas <[EMAIL PROTECTED]> 2008-05-27 14:03:37 PST --- It is the class that is non-public. There is, simply, no bug here. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email -

DO NOT REPLY [Bug 45065] RequestDispatcher restricts access to ApplicationHttpRequest

2008-05-27 Thread bugzilla
https://issues.apache.org/bugzilla/show_bug.cgi?id=45065 --- Comment #8 from Paul Copeland <[EMAIL PROTECTED]> 2008-05-27 14:45:58 PST --- You are right. I got it. I need to know the class or interface I am invoking on and not simply the class of the implementing object. Thanks. -- Config