"azalea" wrote : | wschwendt, how about your crud app? | azalea, I'm not writing any CRUD app in the sense that I'm developing something for a commercial client project. I'm not doing anything commercial right now. Roughly speaking, my interest is to find an approach how to systematically develop web apps with Seam. Therefore, I'm trying to get an understanding of the semantics of Seam. Now back to our problem: I'd need to take a closer look at your solution and why it works, before I can comment on it. But I'm still very interested in the original question and the behavior of the ManagedEntityIdentityInterceptor. EntityHome looks to me like a general seam component; the culprit for the caching behavior appears to be the ManagedEntityIdentityInterceptor. And given that EntityHome is a general component, I'd expect to get this caching behavior probably for other stateful components as well. Therefore, I'd be very interested in the answer whether the current behavior of ManagedEntityIdentityInterceptor is really as intended or whether it is a bug. At least it looks to me like a potential bug, but my understanding is still limited, so I'm not sure whether I should file it in JIRA. Clearly, if there is a caching behavior caused by ManagedEntityIdentityInterceptor, its semantics should be defined. And it is a basic fundamental feature that really influences seam apps. Comments by Seam gurus would therefore be highly appreciated. regards, Wolfgang View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4063458#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...