After you log out how are you getting back to the page? Are you clicking the Back button or clicking on a link? It sounds like the behavior you see when clicking a Back button and the browser has kept the value of text fields as it isn't doing a reload.
I am redirecting the page or by pressing the button (which is just a normal link with
or just hitting the page again,
Of course I'm not using the back button,
More to say,
After pressing the button that redirects to the form a new long running conversation is started,
When I check in debug.seam, I see the new conversation and the component already has all the properties filled up with the old data,
So for every new conversation that is started, I see the old data within the component attached to the created conversation,
Weird, isn't it? :-)
I have a seam stateless EJB bean component that is scoped as CONVERSATION with some properties, something very simple as:
This will cause you all sorts of problems with field data consistency (and others). Read about what @Stateless really means.
Weird, I have another class that always worked,
Yes, I could figure out that sometimes the stateless bean instance keeps alive for longer time although I was sure it is really stateless :)
So what's the best way? this component is annotated as stateless since it is based on many other stateless/stateful beans,
so I thought the safest way is to inject EJBs by container,
I can use initialContext in order to use EJBs but it's less comfortable and less elegant,
What are my other options? I can make the component a normal POJO , make all EJBs seam components and inject all the EJBs via @In but I'm not sure it is safe enough to inject many stateless/stateful EJBs that way, is it?
What's the best from both options? or there's a better approach?