12 messages in net.java.dev.osworkflow.usersRe: [Opensymphony-workflow] Approachi...| From | Sent On | Attachments |
|---|---|---|
| Luca Masini | Aug 10, 2005 12:23 am | |
| Abhishek | Aug 10, 2005 6:29 am | |
| Luca Masini | Aug 18, 2005 11:47 pm | |
| Luca Masini | Aug 19, 2005 5:33 am | |
| Abhishek | Aug 19, 2005 12:19 pm | |
| Abhishek | Aug 19, 2005 12:28 pm | |
| Luca Masini | Aug 19, 2005 1:11 pm | |
| Luca Masini | Aug 19, 2005 1:13 pm | |
| Abhishek | Aug 19, 2005 1:23 pm | |
| Abhishek | Aug 19, 2005 1:26 pm | |
| Abhishek | Aug 19, 2005 1:28 pm | |
| Costin Leau | Sep 6, 2005 2:05 am |
| Subject: | Re: [Opensymphony-workflow] Approaching a new HibernateStore | |
|---|---|---|
| From: | Luca Masini (l.ma...@infogroup.it) | |
| Date: | Aug 19, 2005 1:11:27 pm | |
| List: | net.java.dev.osworkflow.users | |
for point 1, if we have a list then we can get the steps in the order in which they were executed. Using a bag with order-by should solve this problem. I think the retrieving the steps in order might be important for some applications. so bag or list both should be ok. but using a bag would need changes to the database schema ?
Is not so clear for me, which is the order in HistoryStep ? Start date or Finish date ? Using a bag we have Set semantic and List interface, so no change in DB schema and object contracts.
for 2, yes, having a version number on WorkflowEntry should be great. I am having some problems using entry as the entry point for everything. These problems are most likely due to hibernate "write behind". May have to flush the session manually.
Which kind of problems ? Please be more precise, may be they are important for the design. Ciao.
--------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=5360&messageID=13278#13278
------- End of Original Message -------