I should clarify the following: > There shouldn't be a publish() method on the producer *client* - a client > can't publish methods on behalf of a resource.
This does not mean that a resource must publish all of its own messages; in fact, it's perfectly reasonable for another resource to monitor a second resource and publish notifications on its behalf. The WSDM Event Format (WEF) recognizes this and has fields for "reporter" and "source" in order to distinguish between who sent the event and who caused it. However, even in this case, the reporting resource should use its NotificationProducer capability to call publish() - not send a web service request to the source resource and tell *it* to publish. In the case where you're publishing a notification about another resource, the consumer of the notification can see from the HTTP/WS-A headers that it came from the reporter, but it will use the info inside the message to discern what resource the message is really about. Dan Daniel Jemiolo/Durham/[EMAIL PROTECTED] wrote on 09/22/2006 12:14:22 PM: > There shouldn't be a publish() method on the producer *client* - a client > can't publish methods on behalf of a resource. From within your > server-side code, you can publish messages using the NotificationProducer > capability. This is covered in one of the "how-to" articles in the > reference manual - from /docs/index.html, go to Documentation -> Reference > Manual and look under the "How To..." section. > > Additionally, if you take a look at the client code, you'll see that it > extends NotificationProducerClient and adds the getter/setter methods for > manipulating the resource properties described in the WSDL. The > NotificationProducerClient class includes the WSN operations > (subscribe/getCurrentMessage) and includes other basic client methods like > setTrace(). If your IDE has context-assist/intellisense, you can see the > methods available from the base client classes; if you're using a text > editor, check out the JavaDoc for: > > org.apache.muse.ws.notification.remote.NotificationProducerClient > > Dan > > > "José Antonio Sánchez" <[EMAIL PROTECTED]> wrote on 09/22/2006 12:04:51 > PM: > > > Hello, I'm testing MUSE 2 and I'm following the tutorial to learn how it > works. > > I have used the sample-wsn-producer.wsdl file to generate the service > > and the proxy but in the generated WSResource interface I get only > > operations to insert, update and delete resource properties, but not > > operations like publish. Also, there is no setTrace method. > > > > -- > > Saludos. > > José Antonio Sánchez > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
