From what I see in the pubscribe documentation (e.g http://ws.apache.org/pubscribe/dev_guide/producer.html), this Resource is supposed to have a getter by the name: yourResource.getTopicSet().

 

I produced a WSDL file (using the MUSE FileSystem sample) and executed the ant "Generate" target.

The Resource code generated by the build process doesn't contain a getter by the name getTopicSet(). Further more, it seems as if the Service is expected to implement the Notify function (e.g: public void notify(NotifyDocument notifyDocument)) and it doesn't.

 

Are there any known issues with the MUSE code generator?

 

Asaf Lahav

VP R&D, Prima Grid LTD.

Cellular:  972-54-4717955

Phone:   972-3-6540255

Fax:       972-3-6540254


From: Campana Jr., Salvatore J [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 4:03 PM
To: [email protected]; [email protected]
Subject: RE: topics/notifications via MUSE

 

take a look at the Pubscribe documentation and examples.  Muse extends Pubscribe, which means you do things the same way,...

 


From: Asaf Lahav [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 29, 2006 6:52 AM
To: [email protected]; [email protected]
Subject: topics/notifications via MUSE

Hi,

What is required if I want to utilize MUSE to generate WSNT notifications and topics on my web service?

What I'm trying to accomplish is to utilize MUSE to enable the publishing of custom Notifications.

e.g,

Let's say I have a scenario of WSRF web-services which are managing a hardware store. And I want to be able to publish notifications to subscribers indicating that the storage level decreases below a preconfigured level.

What I would like MUSE to provide is the means to enable creation of a topic that would enable consumers subscribe to it so they will get the notification.

 

What am I supposed to include in the MUSE WSDL (or anywhere else) in order to accomplish that or similar results?

 

Asaf Lahav

VP R&D, Prima Grid LTD.

Cellular:  972-54-4717955

Phone:   972-3-6540255

Fax:       972-3-6540254

 

Reply via email to