atom feed12 messages in net.java.dev.osworkflow.usersApproaching a new HibernateStore
FromSent OnAttachments
Luca MasiniAug 10, 2005 12:23 am 
AbhishekAug 10, 2005 6:29 am 
Luca MasiniAug 18, 2005 11:47 pm 
Luca MasiniAug 19, 2005 5:33 am 
AbhishekAug 19, 2005 12:19 pm 
AbhishekAug 19, 2005 12:28 pm 
Luca MasiniAug 19, 2005 1:11 pm 
Luca MasiniAug 19, 2005 1:13 pm 
AbhishekAug 19, 2005 1:23 pm 
AbhishekAug 19, 2005 1:26 pm 
AbhishekAug 19, 2005 1:28 pm 
Costin LeauSep 6, 2005 2:05 am 
Subject:Approaching a new HibernateStore
From:Abhishek (oswo@opensymphony.com)
Date:Aug 19, 2005 1:23:12 pm
List:net.java.dev.osworkflow.users

if you look at the current mapping the schema has a column for list index which
will not be required once the mapping is changed to bag. Object contract would
not change but the DB schema may change.

I had problems because of unsaved-value attribute of CurrentStep and
HistoryStep. The mapping file had unsaved-value as -1 and when a new current
step was created it had 0 as the value in id field. If this is the case then
hibernate thinks that the entity is already saved and does not issue a insert
sql statement. It works perfectly after removing the unsaved-value attribute.

I have one concern which you have not addressed till now. Are you planning for this store to use its own sessionFactory or it could also
use a session factory supplied by the application ?

--------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=5360&messageID=13284#13284