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.
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
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.