ConversationUtils.cacheWindowId() ignores session invalidation --------------------------------------------------------------
Key: EXTCDI-92 URL: https://issues.apache.org/jira/browse/EXTCDI-92 Project: MyFaces CODI Issue Type: Bug Components: JEE-JSF20-Module Affects Versions: 0.9.0 Environment: MyFaces Core 2.0.3 trunk, OWB 1.0.0, Tomcat 6.0.29 with Glassfish EL libs Reporter: Jan-Kees van Andel A while ago, I raised issue MYFACES-2979. I now wanted to fix and commit it, but I don't get this exception anymore, because I added CODI to my application a while ago. Reason: After invalidating, CODI re-initializes the Session, so it's not null anymore and the DebugPhaseListener stuff doesn't throw an exception anymore. However, I don't think this behavior is desirable. After all, I've invalidated the session in my application code, so I don't want any framework to re-initialize it without questioning. I can't come up with an example of anything that really breaks because of this, but it's not very nice and efficient. It happens in the following method: org.apache.myfaces.extensions.cdi.jsf.impl.util.ConversationUtils#cacheWindowId() on line 191. Wdyt? -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.