Could pl. let me know how to set inverse attribute using annotations. I read inverse equivalent is mappedby.. however for a cose like this..

Map where DateTimeSpec is create and not saved yet but added to this map. When the class having this map instance is saved I am expecting all the new one referenced in the map of DateTimeSpec, AbstractTezzD should be saved. Also, pl. observe that map holder is also a class which is part of inhericance chain for value of the map..

public final class TimeTezzD extends AbstractTezzD
{
@OneToMany(fetch = FetchType.EAGER,
cascade = CascadeType.ALL)
@JoinTable(name = “tbl_time_tezzds_map”,
joinColumns = {@JoinColumn(name = “fk_time_tezzds”,
nullable = false)},
inverseJoinColumns = {@JoinColumn(name = “fk_abs_tezzds”,
nullable = false)})
private final Map timeTezzDMap = new HashMap();

..

Workaround I see is this..

Every DataTimeSpec object I added I save it first and then add to this map. then it is working.. however looking for jpa system to auto take care of it.. rather than giving the

[java] There was 1 error:
[java] 1) testValid(com.tejasoft.dialer.model.bdo.tns.time.test.TestTimeTez
zD)org.hibernate.TransientObjectException: object references an unsaved transien
t instance – save the transient instance before flushing: com.tejasoft.dialer.mo
del.bdo.tns.time.DateTimeSpec

Any clues would help..

Regards,
Raja Nagendra Kumar,
C.T.O
http://www.tejasoft.com

However, the fact that I had no unsaved-value was the problem, because Hibernate believes that “0″ is an unsaved-value by default. Took me a whole day to realize this and put a “unsaved-value=-1″ in the mapping.

I had this problem and it was related to my IInterceptor implementation.

I used a base Persister class to give nHibernate a hint to determine if a class was already in the DB.

As i was developing a web app there were occasions where i had to manually create an object using an ID. i.e Person myPerson = new Person(17765);

I then added this Person to a collection of Another object. When attempting to persist this object nHibernate checked myPerson.IsSaved which was false because i hadn’t actually loaded this object from nhibernate. Because it was false nHibernate assumed it was unsaved so threw the exception being discussed (after all it didn’t want to go and attempt to create an insert in my join table using the primary key of an object that didn’t exists in the database).

Anyhows, changing my code to this resolved the error:
Person myPerson = new Person(17765)
myPerson.IsSaved = true;

Please note that i new a person with id 17765 already existed but i didn’t want to keep going to the DB everytime i added a person to the collection. (Going to the db and getting the person would also have prevented the error. i.e myPerson = session.Get(17765); because hnibernate knows it exist in the db when i comes to save the association)

Now…Another scenario where you could get this exception would be:

I create a new Person who does not have a record in my DB:
Person myPerson = new Person(99999);
myPerson.IsSaved = false;
If I then add this person to the collection of my other object, lets call it “Bus”….so….
Bus.Passengers.Add(myPerson)

When nhibernate attempts to save Bus if i don’t have cascade=”save-update” set in Bus.hbl.xml file then once again nhibernate will not want to insert into the join table using a myPerson.Id which does not exist in the Person database table.

Alternatively if i don’t want to set cascade in Bus.hbl.xml then i must explicitly save myPerson so that the record does exist before nhibernate goes to insert that join record.

Phew. Rambled a bit there, hope it helps someone.