Hi Tom,
Tank you for the answer. I read your thread. The funny thing is that
I do the same for another workflow system, called jbpm.
Makes sense really, a workflow engine is an obvious consumer of dynamic invocation code. I took a look at your website, it's interesting stuff. You might be able to pull out some of our graphical workflow construction environment if you don't already have that capability, it's all LGPL. Let me know if you'd be interested in some kind of collaboration and we can continue this offline.
But all works fine with the default Bean serializer. I don’t like to create my own serializer.
Well, you don't really have to, just use the existing ElementSerializer.
I would like to configure the Bean serializer to stop serializing at defined classes.
Wouldn't this result in you not getting your return information back? When you say 'stop serializing' what _exactly_ do you mean?
Cheers,
Tom
