| Key: |
SHALE-296
|
| Type: |
Bug
|
| Status: |
Resolved
|
| Resolution: |
Fixed
|
| Priority: |
Blocker
|
| Assignee: |
Unassigned
|
| Reporter: |
Mario Ivankovits
|
| Votes: |
0
|
| Watchers: |
0
|
|
If you were logged in you would be able to see more operations.
|
|
|
|
one side effect is, that a error page which should be shown is no longer possible to view the exception as the lifecycleListener has removed it from the map.
From the comment a few lines above the code piece in queston I guessed what was the original intention.
|
|
Description
|
one side effect is, that a error page which should be shown is no longer possible to view the exception as the lifecycleListener has removed it from the map.
From the comment a few lines above the code piece in queston I guessed what was the original intention. |
Show » |
| Repository |
Revision |
Date |
User |
Message |
| ASF |
#451376 |
Fri Sep 29 18:20:32 UTC 2006 |
craigmcc |
Reduce the set of request scoped beans that are forcibly removed in
requestDestroyed(). In theory this should not be necessary, because the
container is supposed to call requestDestroyed() only *after* all
request processing has been completed. Alas, this is apparantly not
true in all cases. Therefore, we should only delete instances for which
we are going to create a destroy() callback for (AbstractRequestBean and
ViewController).
Based on a patch by Mario Ivankovits.
SHALE-296
|
| Files Changed |
MODIFY
/shale/framework/trunk/shale-core/src/main/java/org/apache/shale/view/faces/LifecycleListener.java
|
|
lifecycleListener removes too many servletRequest attributes in case of requestDestroyed
