The 09/2004 spec seems to offer identifiers for WSDL, XSD, and WS-Policy, but WSDL was the only one that made sense for us given the effort we go to in resolving the WSDL and making it available to the client (without resolving the imports, you'd have to do a lot of plumbing to get all the docs on disk and then parse them). I guess my question is, if you use the XSD identifier, do you want all schema files? When you say "the XSD", it implies there is one - perhaps the one you wrote, and not the WS-* XSDs. Let me know what you meant so I can offer a suggestion on achieving this.
Also - the response you get is the closest WS-MEX has as far as indicating "no metadata". The spec doesn't have any faults for GetMetadata, so the simplest thing was to return no metadata elements for the given dialect/identifier pair. Dan "Jared A. Zebedee" <[EMAIL PROTECTED]> wrote on 03/27/2007 05:55:44 PM: > Greetings all, > > I am attempting to use the GetMetaData operation to retrieve the XML > Schema Document for a MUWS Resource Manager. > > The GetMetaData operation accepts 2 parameters: Dialect, and Identifier > > According to the specification, acceptable values for Dialect include: > > http://www.w3.org/2001/XMLSchema (For retrieving the XML Schema > document) > http://schemas.xmlsoap.org/wsdl/ (For retrieving the WSDL document) > > I have successfully used the GetMetaData operation to obtain the entire > WSDL document. However, when I try to use it to obtain the XML Schema > Document, the response I receive is empty (I get a proper response with > no Metadata included). In both cases, I am specifying the URI of my > Resource Manager as the Identifier. > > Does anyone know if this operation has yet been fully implemented in > Muse? I would like to be able to retrieve the XML Schema Document, > rather than the entire WSDL document. For the time being, I can filter > through the WSDL document to obtain the data I need, but this is not > very efficient. > > Thank you. > > Jared Zebedee > [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
