ws-tx-implement message
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]
Subject: Re: [ws-tx-implement] Scenario 12 details
- From: Doug Davis <dug@us.ibm.com>
- To: ws-tx-implement@lists.oasis-open.org
- Date: Wed, 4 Oct 2006 16:41:33 -0400
All,
The IBM implementation will expect
the URL to have a query parameter:
ie.
http://www.soaphub.org/wstx/services/InteropService?PA=1
and
http://www.soaphub.org/wstx/services/InteropService?PA=2
And of course these will only have meaning
for scenario 12.
thanks
-Doug
Ian Robinson <ian_robinson@uk.ibm.com>
09/28/2006 11:04 AM
|
To
| ws-tx-implement@lists.oasis-open.org
|
cc
|
|
Subject
| [ws-tx-implement] Scenario 12 details |
|
On the last telecon we agreed that BA scenario 12 (MixedOutcome) should
retain the use of 2 PAs (PA1 and PA2). We did not require any specific
implementation strategy for CS to distinguish which of the PAs the separate
PS1 and PS2 registrations come from. One strategy would be to use distinct
RegService EPRs in the 2 contexts but this is not an interoperability
concern and therefore does not need to be elaborated on in the scenario
doc.
Each provider currently publishes a single URL for their interop endpoint
(per transport binding). This scenario requires either 2 URLs to be
specified for the participant role or a single URL with a query parameter
to distinguish the 2 PAs. It doesn't matter which strategy is adopted so
long as the different endpoint providers agree.
Regards,
Ian
[Date Prev]
| [Thread Prev]
| [Thread Next]
| [Date Next]
--
[Date Index]
| [Thread Index]
| [List Home]