Comparing current revision with historical revision 1.
From lines 0 to 1 changed to lines 0 to 1:
You really have to understand how Seam works to understand this message. You see this issue most often during development when using the hot deploy classloader. When Seam dumps and reloads the hot deployable classes, instances of those classes may still existing in an active long-running conversation. When you attempt to use that conversation, worlds collide. You just need to flush the session.
You really have to understand how Seam works to understand this message. You see this issue most often during development when using the hot deploy classloader. When Seam dumps and reloads the hot deployable classes, instances of those classes may still existing in an active long-running conversation. When you attempt to use that conversation, worlds collide. You just need to flush the session.