CDI ConversationScoped long-running Bean not working?

Short answer : Yes, this is the correct behavior.

Short answer: Yes, this is the correct behavior. Long answer: A conversation represents a "unit of work", which a such has to be demarcated explicitly. This is done with the explicit call of conversation.begin() - as you are doing already.

Should you want to use the same conversation over more than one request, you have to propagate it - this is what you are not doing :-) When you propagate a conversation, a conversation-id is appended to the request. This tells the container which conversation is wanted. When you just hit the refresh button without a conversation-id in your request a new conversation is generated for each request.

From the documentation: The conversation context automatically propagates with any JSF faces request (JSF form submission) or redirect. It does not automatically propagate with non-faces requests, for example, navigation via a link. If you need to propagate it manually, just add the conversation-id to the request: All that and much more is explained here.

" If you disagree, bring it to meta. – BalusC Mar 30 at 19:06 Acknowledged :-) – jan groth Mar 30 at 19:16.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.