I'm not sure defining <wsdl:message/>s for notifications is valid - after all, aren't all notifications already part of a <wsdl:message> (wsnt:Notify)? WS-N TopicSet documents have the messageType info (which gives the root names of the message content elements), but this doc is not presented in full from a WS-* endpoint. I believe it's supposed to be design-time metadata.
One idea that may be easy to implement is to use the RMD doc - just extend the <wsrmd:Property/> element for the wsnt:TopicExpression property and add your own custom metadata elements to it, like so: <wsrmd:Property name="wsnt:Topic" mutability="constant" modifiability="read-only"> <cisco:MessageContent>some xpath or qname to describe the content</cisco:MessageContent> </wsrmd:Property> Dan "Vinh Nguyen \(vinguye2\)" <[EMAIL PROTECTED]> wrote on 02/15/2007 08:35:53 PM: > Muse currently only has support for defining operation message types, > but not for notification message types. Would this be something useful? > > Related to my previous posting, I have an issue where an underlying > system generates a notification consisting of an array of elements. > Muse doesn't have support for publishing an array of elements. Even if > it does, the client has no way of knowing the data structure of a > notification message, unless they have previous knowledge of the > underlying system and knows to expect certain data types. So I thought > that defining a notification message type in a wsdl might be helpful. > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
