Question

We have a search form where the filter is bound to a property on a managed bean (session scope). It’s not component binding, its property binding like <h:inputText value="#{searchBean.filter}"/>.

Submitted data from different machines (different sessions, then) is getting mixed. You search “john”, and get “mary” just because the guy beside you have just searched “mary”. The value of your searchBean.filter is getting his submitted data instead of yours.

I’ve already googled around a lot and found no solution, just an ocurrence of the same problem.

Have anybody faced this issue already? Any clues?

Thanks!

Answer 1

This can have two causes:

1. The bean is actually in application scope.
2. The property in question is declared static.

To fix 1), just ensure that it’s in session scope.
To fix 2), just remove the illegal modifier.