Simon Nash wrote:
Simon Nash wrote:
(cut)
Instead of trying to establish callback wires all over the place,
which will not fly anyway as soon as 2 references with callback are
wired to a single service, flow the endpoint reference of the
callback service representing the client in the SCA request message
and use it to direct the callback.... "in context" as suggested by
Raymond in thread [1].
These callback wires are already being established and AFAIK this
does work
in the case you describe. The callback wire is selected based on the
forward wire that was used. I'll write an itest to verify that this is
working correctly.
I created this itest and verified that it runs correctly. I have
attached
it to TUSCANY-1503 as a patch.
Simon
Ok, this works now, but this JIRA is talking about a different design where:
- callbacks will be represented as (almost) regular services and references
- there will be no special processing anymore for callback wires in the
core runtime.
That's why I said in my comment "will not fly" instead of "does not fly"
:) Will this particular configuration still work with the new design,
and without all the special processing we currently have for callback wires?
In particular, with the new proposed design, a service with a callback
will be represented as a reference, if the service was wired to by
multiple clients, the reference representing the callback will have to
be wired to these multiple clients (and on them the services that
represent callbacks). This looks like a reference with multiplicity > 0,
and it doesn't look to me like the proper way to represent this wiring.
At least that alone won't allow us to select the correct client to callback.
So I think we should at least evaluate both options (establish regular
wires vs flowing endpoint references) in the context of this new design.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
