Home/ Questions/Q 8728779
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T08:42:50+00:00

I currently have a single entry point (through a @WebService ) that manages a

  • 0

I currently have a single entry point (through a @WebService) that manages a list of request, each of them being a DAO operation (ie createEmployee, createCompany, etc…).
A Company has multiple employees and when my list of commands is the following:

client call #1:
1. createCompany
2. createEmployee
3. addEmployeeToCompany

client call #2:
1. findAllCompanies

I get all the companies, but not the employees associated to them.
If i redeploy the app, and to the findAllCompanies command i comes with all the info (company + employees), seems some persistence bug.
All my beans are stateless (should they be statefull?) and my entity manager is injected on them (should it be only injected on the webservice bean and passed to the others?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The problem was due to JPA’s cache.

    the query worked fine the first time, and all the subsequent queries feed themselves from the cache.

    oracle docs had the answer, and this can be configured on multiple ways:

    • by configuring the persistence.xml and seting the entity’s cachable parameter (shared-cache-mode)
    • by setting the EntityManager’s properties javax.persistence.cache.retrieveMode and javax.persistence.cache.storeMode
    • by setting javax.persistence.cache.retrieveMode and javax.persistence.cache.storeMode on EntityManager’s find or refresh
    • 0