|
Mantis - Resin
|
|||||
| Viewing Issue Advanced Details | |||||
|
|
|||||
| ID: | Category: | Severity: | Reproducibility: | Date Submitted: | Last Update: |
| 4117 | minor | always | 07-12-10 10:13 | 08-03-10 17:02 | |
|
|
|||||
| Reporter: | ferg | Platform: | |||
| Assigned To: | alex | OS: | |||
| Priority: | normal | OS Version: | |||
| Status: | closed | Product Version: | 4.0.8 | ||
| Product Build: | Resolution: | fixed | |||
| Projection: | none | ||||
| ETA: | none | Fixed in Version: | 4.0.10 | ||
|
|
|||||
| Summary: | 0004117: cross-context include does not return proper context | ||||
| Description: |
(rep by Brian Deng) I've found a difference between v3.1 and v4.0 with respect to context dispatching. Can you confirm whether this change is by design or a bug? Here's the scenario: I have 2 different webapps (call them appa and appb) From appa, I do the following: servletContext.getContext("/appb").getRequestDispatcher("/Controller").include(request,response) Within the servlet code for /appb/Controller, request.getContextPath() returns "/appb" in 3.1 but it returns "/appa" in 4.0 What is the correct behavior for include() when called across webapp contexts? |
||||
| Steps To Reproduce: | |||||
| Additional Information: | |||||
| Relationships | |||||
| Attached Files: | |||||
| Notes | |||||
|
|
|||||
|
|
||||