10 messages in net.java.dev.osworkflow.usersOSWorkflow in a 3-tier environment| From | Sent On | Attachments |
|---|---|---|
| fschroder | Sep 20, 2005 2:35 pm | |
| Luca Masini | Sep 20, 2005 3:00 pm | |
| fschroder | Sep 21, 2005 5:42 am | |
| Luca Masini | Sep 21, 2005 7:28 am | |
| fschroder | Sep 21, 2005 11:53 am | |
| Luca Masini | Sep 21, 2005 11:47 pm | |
| Abhishek | Sep 22, 2005 8:51 am | |
| fschroder | Sep 22, 2005 11:19 am | |
| Luca Masini | Sep 22, 2005 2:27 pm | |
| fschroder | Sep 26, 2005 11:23 am |
| Subject: | OSWorkflow in a 3-tier environment | |
|---|---|---|
| From: | fschroder (oswo...@opensymphony.com) | |
| Date: | Sep 22, 2005 11:19:20 am | |
| List: | net.java.dev.osworkflow.users | |
You're right about that, but I was trying to use hibernate's feature when the WF
instance is back on the server (to persist it).
I tend to agree with you, I believe I'm trying to use oswf in a way it wasn't
intended to, so I think I'll stick with the remote call.
Federico.
PS: another big detail: I don't see any class implementing serializable...
you said earlier that the workflow will be used in a remote client so hibernate session will not be available. So no features of Hibernate will help you at the remote client. Also if you are writing your own functions and conditions then also you may run into problems as they may have to access some of your domain objects. It seems to me that it would be much safer/simpler for you to live with the remote call. Also as a strategy, you may have all workflow interaction take place at the server instead of the remote client. If anything happens at the client which requires the workflow just go to the server.
--------------------------------------------------------------------- Posted via Jive Forums http://forums.opensymphony.com/thread.jspa?threadID=6932&messageID=15639#15639