[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsdm] Concrete, practical interop question
Repeating just to confirm: there is no interop for the June F2F? Does anyone want to do any informal interop in a scenario similar to what I described? Thanks, > -----Original Message----- > From: Murray, Bryan P. [mailto:bryan.murray@hp.com] > Sent: Friday, May 28, 2004 2:02 PM > To: Mike Clements; wsdm@lists.oasis-open.org > Subject: RE: [wsdm] Concrete, practical interop question > > Mike, > > You are probably talking about the WSDM f2f in April as there will not > be any interop testing for the June f2f. > > Your scenario and assumptions about the answers are correct. For the > April f2f we made a simplifying assumption that one manageability web > service supports exactly 1 manageable resource. We also > assumed that we > did not need to abide by the WS-Addressing rules and did not > include any > WSA SOAP headers. Thus, the WSDL described operations that > pertained to > 1 manageable resource and a client could assume that messages could be > addressed exactly as the WSDL specifies. > > These simplifying assumptions were made for the purposes of > the interop > event and may not apply to the WSDL standards as they evolve. > > Bryan > > -----Original Message----- > From: Mike Clements [mailto:mikec@actional.com] > Sent: Friday, May 28, 2004 1:48 PM > To: wsdm@lists.oasis-open.org > Subject: [wsdm] Concrete, practical interop question > > > This question pertains to the interop for the upcoming F2F. > > C: Consumer: consumer of manageability provider > MP: manageability provider > MR: managed resource > > Scenario: > > C is given an URL to obtain the WSDL for MP. > From that WSDL, C obtains the URL to invoke calls on the MP. > C can now make a call to MP. > But these calls are generic such as "getStatus" and do not explicitly > mention an MR. And the MP has no operation for C to ask what MRs it is > managing. So C must already (somehow) know about a MR that MP is > managing. And C must (somehow) "identify" this MR in its call > to MP. But > since operations on MP don't specify MR as a parameter, C > must identify > MR in the SOAP header, or URL or something like that. > > Here is what I *think* the answers to the questions are: > > C assumes that the URL it got from the MP WSDL is unique to one > particular MR. Thus, C doesn't need to identify a MR in each call, > because all calls it sends to the MP at that URL, > automatically apply to > some particular MR. Thus, C just calls operations on MP without > identifying any MR. > > If that is so, then each MR will have its own unique URL to obtain for > the WSDL for its MP, and that WSDL will specify a MP URL which is > specific to that MR. > > Is that right? > > Michael R. Clements > mikec@actional.com > FREE! Actional SOAPstation Developer Version > Web services routing, security, transformation and versioning > http://www.actional.com/sstdownload > > To unsubscribe from this mailing list (and be removed from > the roster of > the OASIS TC), go to > http://www.oasis-open.org/apps/org/workgroup/wsdm/members/leav > e_workgrou > p.php. > > >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]