Thanks Mauricio, comments inline
Maciej
On 31.07.2012 19:45, Mauricio Salatino wrote:
Hi Maciej,
Kudos for the post! It's a really nice example.
I have a couple of questions about parameters to the
invocation and how we can process the results for the
invocation.
What are the limitations for such constructs?
First limitation, in general is that WSDL is stored in process
definition which makes moving between environments (dev, test, qa,
prod) bit difficult but from the other hand it alows tooling to
build up interface and operation definitions. Comments welcome here
:)
Most of the solutions out there provide XPATH for mapping
different pieces of information, and that's definitely something
that will be required if the user wants to integrate against
legacy web services.
Difference here is that for invocation handler expect that it has
correct message to be sent out. What you had in mind could be
probably covered by assign/transformation on data association level
in bpmn2 model. But if you think that is not enough we could
elaborate bit more to see what are the use cases.
What about async executions? is that being handled by CXF?
Yes, this is handled by CXF, when invoking the operation you could
provide callback to get result once they are ready.