[Bug 62] Shall the begin operation of CTX service include as optional parameter the ALS configuration identifier?

[bugzilla-daemon@arjuna.com]

http://services.arjuna.com/wscaf-issues/show_bug.cgi?id=62

rjimenez@fi.upm.es changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
            Summary|Shall the begin operation of|Shall the begin operation of
                   |CTX service  include as     |CTX service  include as
                   |optional parameter the ALS  |optional parameter the ALS
                   |configuration identifier?   |configuration identifier?



------- Additional Comments From rjimenez@fi.upm.es  2004-02-25 12:39 -------
Page 29 of WS-CTX states that CTXService operations are contextualiased with the
current context and therefore propagate the ALS-configuration identifier of the
current context. It seems that this is used as justification to not pass as
explicit argument the ALS-configuration identifier in the CTXService operations.
This scheme would work to start nested activities (enclosed in existing
activities) and to end activities. However, when a top-level activity is to be
started, there is no active context that could be propagated. How does then know
the context service which ALS-configuration identifier should be used for the
new top-level activity?
A possible solution to the problem would be to include a begin operation in
which the ALS-configuration identifier is passed explicitly as an argument to
the begin operation (or as an optional argument of the begin operation). 

In the same issue if applications are allowed to start activities with different
ALS-configuration identifiers, again these identifiers should be passed
explicitly in the begin operation.





------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.