Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an @PostConstruct init() function in my backing bean that performs a lengthy database query.
The backing bean is @SessionScoped.
Every time I perform an Ajax query, I hit that init() and the database query fires off again.
Do I need to check life cycle phase in my init() before firing the database query? Or should I store the details in a more persistent object such as the current User?
Best regards,
Alan
@PostConstructfor@SessionScopedbeans is executed only once per user session, so it is the correct place to initialize the bean. Make sure the bean is indeed in session scope, and that the multiple executions of it are not actually coming from different users (=> sessions)