Subject: RE: [wsrp] Comment
I don't think the spec mentions rpc-style. The way the API is defined in the spec is supposed to be the easiest to understand, not an official schema definition, so the fact that the top level parameters are actually wrapped in a structure (in all the methods) is abstracted. It is true that the WSDL is the correct definition. Yossi. -----Original Message----- From: Subbu Allamaraju [mailto:email@example.com] Sent: Thursday, December 02, 2004 4:31 PM To: firstname.lastname@example.org Subject: [wsrp] Comment Any comments regarding this question in email@example.com? It looks like the wsdl uses document-style descriptions, but the spec mentions rpc-style. Regards, Subbu From: ada_dynamis <firstname.lastname@example.org> Reply-To: email@example.com To: firstname.lastname@example.org Date: Thu, 02 Dec 2004 11:38:03 -0000 Subject: [wsrp] WSRP Spec and actual implementation? Reply | Reply to all | Forward | Print | Add sender to contacts list | Trash this message | Report phishing | Show original Hi all! I am just browsing through documentation and was looking at the SOAP messages going between one consumer and one producer (Vignette and Sun). What puzzles is that in the interface specification, the method getServiceDescription is described differently than in the specification itself. I believe that the one in the interface-spec is the right one. For instance, the spec (wsrp-specification-1.0-cs-1.0-rev2.pdf) points that: ServiceDescription = getServiceDescription(RegistrationContext, desiredLocales); whereas the interface says something like this: ServiceDescription = getServiceDescription(getServiceDescription); where getServiceDescription is a complex type representing RegistrationContext and desiredLocales. It may as well be, that I don't quite understand the interface definition... Any input on that? Thanks, Miha 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/wsrp/members/leave_workgrou p.php.