> Without any specifics on what to expect back from the
> Producer web service, it seems that the client is
> helpless to correctly process the content of
> notification messages.
Yes. The dreaded xsd:any. This is one of the difficult parts of the WS-*
specs - over-reliance on xsd:any. Muse can't really change the WSN spec in
that regard, but the spec does provide things like topics (<wsnt:Topic/>),
which allow you to make assumptions about what will be in the message body.
It's not a schema, but it gets you a bit further.
> Also, how does the Provider web service specify and advertise to
> the client the supported filters & filtering mechanisms so that
> the client can request valid filtering?
This is the goal of the WSN topics.
> Where is this type of specification/modification/addition to
> the standard WSDLs covered in the Muse documentation (or even
> as topics on this forum)?
http://www.ibm.com/developerworks/autonomic/library/ac-musewsn1.html
http://www.ibm.com/developerworks/autonomic/library/ac-musewsn2.html
Dan
david2 <[EMAIL PROTECTED]> wrote on 06/10/2007 08:35:45 AM:
>
> The content of unfiltered subscription requests sent to a WS-Notification
> Provider web service are pretty clear based upon the
> WS-BaseNotification-1_3.wsdl document. However, the notification message
> sent back to the Consumer web service is pretty generic and appear to
allow
> anything or even nothing. How is the organization providing the Producer
> web service to specify the return interface to client organizations who
wish
> to provide the Consumer web service whose URI is sent in the subscription
> request? Without any specifics on what to expect back from the Producer
web
> service, it seems that the client is helpless to correctly process the
> content of notification messages.
>
> Also, how does the Provider web service specify and advertise to the
client
> the supported filters & filtering mechanisms so that the client can
request
> valid filtering?
>
> Where is this type of specification/modification/addition to the standard
> WSDLs covered in the Muse documentation (or even as topics on this
forum)?
> --
> View this message in context: http://www.nabble.com/Specifying-
> Message-Content-sent-to-WS-Notification-Consumer-tf3897276.html#a11048238
> Sent from the Muse User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
