Note that there are some explanatory texts on larger screens.

plurals
  1. USdepthfirstdesigner
    primarykey
    data
    text
    plurals
    1. CO@alfa64 My application is a massively multiplayer social game that pushes critical game state updates dynamically to specific clients in real-time. The catch is that a usual usecase involves a player signing on for couple minutes, probably 15 at the max, before signing off. This essentially wastes at least 85% of (presently) the most expensive resource on app engine, making it utterly non-viable despite its fantastic functionality.
      singulars
    2. COAh thank you Tahir! I believe you've helped me locate the problem. When a user logs in, I use a HQL query to load the corresponding user. My problem is that I was using setters to make the current Session's bean correspond to the databases' bean properties, and I embarrassingly didn't include a setter for the Pet Collection. Is there a better way of re-initializing a Session's bean instead of calling all the setters manually? I tried doing it this way and it doesn't register the changes : FacesContext.getCurrentInstance().getExternalContext().getSessionMap().put("user", newUser);
      singulars
    3. COAs per your suggestion I removed annotations entirely and I am just using XML mapping now. Regarding the eagerly loaded property, I just changed that from LAZY thinking that it might fix the issue. Now that the annotations are gone, I've no longer specified the loading method anywhere. As it stands, the HQL query still returns an empty list even though the HQL query browser correctly gets the results.
      singulars
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload