Skip to content
This repository has been archived by the owner on Mar 20, 2021. It is now read-only.

LifecycleImpl #34

Closed
javaserverfaces opened this issue Aug 3, 2004 · 8 comments
Closed

LifecycleImpl #34

javaserverfaces opened this issue Aug 3, 2004 · 8 comments

Comments

@javaserverfaces
Copy link
Collaborator

For phase listeners, possibly modify the phase processing to allow the
afterPhase method to be called in a finally block. If an error occurs in one of
the Phases, the afterPhase would never be called. This may prevent resource
cleanup and cause memory leaks in developer implementations.

Environment

Operating System: All
Platform: All

Affected Versions

[1.1]

@javaserverfaces
Copy link
Collaborator Author

Reported by jhook

@javaserverfaces
Copy link
Collaborator Author

Was assigned to javaserverfowner

@javaserverfaces
Copy link
Collaborator Author

adamwiner said:
This behavior should be specified in the 1.2 spec. I don't think anything
prevents it from being implemented in 1.1, but the EG should be queried.

@javaserverfaces
Copy link
Collaborator Author

rogerk said:
Moved to 1.2. Also the spec portion of this has been logged as issue #9 in
javaserverfaces-spec-public project.

@javaserverfaces
Copy link
Collaborator Author

@javaserverfaces
Copy link
Collaborator Author

Marked as won't fix on Wednesday, April 19th 2006, 5:44:32 am

@javaserverfaces
Copy link
Collaborator Author

@manfredriem said:
Closing issue out

@javaserverfaces
Copy link
Collaborator Author

This issue was imported from java.net JIRA JAVASERVERFACES-30

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants