I´m currently thinking of the best way to realize data-intensive "workflows" composed of web services (similar e.g. to a BPEL engine). I´ll looking at Axis2 engine for that, but I´m unsure how it could fit my special needs:
What I need to do is to be able to call subsequent operations on a service (e.g. configure(), execute(), getNextResults(), reset(), ..). Background is that these are very long running services which consume and produce potentially some GBs of data. The services are dependend of each other, e.g. execute() may only be called after a predecessor service has successfully executed. Produced data should be re-usable by differend nodes, e.g. passing around and re-generate should be minimized. What do you think of this? What does Axis provide me for this scenario? Should I use, e.g. WS-Resource (Muse) for this? An ESB ? Or should I even consider mapping this into BPEL and use a process engine? (ok, I´ll stop here before it becomes too off-topic) Any remarks would be greatly appreciated. thanks in advance -- Florian --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
