Hi,

I have two entities: Province and City. City has a Province many-to-one field and Province has a one-to-many set of Cities. When I create a new City, and associate it with a Province, the set of cities in the associated Province instance does not get updated within the current session. It doesn't bother me much in a web app, because I open a new session for each request, but in case of a long running desktop app it's a bit inconvenient.

Is there a property that I set to make hibernate update the cache on each update, or is it he cascade property?

Thanks,

Pavel

I am a little confused by your question. If I understand correctly each time you are adding a city to a province you update both sides of the relation which means you have loaded a province from either cache or database and you have, therefore, loaded the list of cities in that province. As a result of update hibernate will reflect the changes to database and updates its underlying cache. The only trick here is when used with JTA you will have to hook up hibernate with the JTA transaction manager so that hibernate knows when everything was happily sent to database and it can keep the changes in its cache.


Farzad-

You may have run into the issue that while FOREIGN KEYS are bi directional in the database in your Java code you have to explicitly set both sides of the relationship.

So just doing City.setProvince(Province) is not enough you also have to do a Province.getCities().add(City). Of course I don't know how your code exactly looks so the above is only an approximation.

I think you have to do 2 things:
- set the "inverse=true" attribute ("mappedBy" in annotations)
- set a cascade option

Carlo