But in examples there are a few statefull compontens with no long running conversation scope.
Does it mean they can be EVENT scoped too, or actually there is differnce beetwen them?
Rafal
Where (sorry, I don't have all the examples memorised ;)?
It's not a statefull compont but Java Beans but there is conversation scope without promotion to long running convesation.
The class is from "drools" example.
@Name("guess")
@Scope(ScopeType.CONVERSATION)
public class Guess
{
private Integer value;
public void setValue(Integer guess)
{
this.value = guess;
}
public Integer getValue()
{
return value;
}
}
I'm starting to realize that if conversation componet is created during the existed conversation it will not be destroyed during render phase of JSF request, but when the existing convesation end.
Am i right?
Yes. Ignoring nested conversations for now, you can have at most one active conversation per browser window/tab. All components that have conversation scope participate in the current conversation (long running or temporary) and are destroyed at the end of the conversation
Ok. So this is answer for my init question:
"What is difference between Event and Conversation if the Conversation componet is not promoted to long running conversation?"
Event component in the above situation will be destroyed, but conversation component will be "added" to existing conversation.