Latha,
Did you generate your code for Filesystem using
Hermes?
If so, in the generated FilesystemResource you should see a
line like this:
TopicUtils.addResourcePropertyValueChangeTopics(...)
This line basically registers all your resource properties
for prop change notifications.....There is no extra code needed to register them
and expose them as Topics...
If this line is not in the generated code, then please
check for the class TopicUtils...If you don't have it, then I need to know what
you are working with...Top of tree should have
this...
So that being said, with
normal generation in Hermes, all your props are setup for prop change
notifications...If you do not want ALL props registered, then follow the steps
in the comment above the TopicUtils line in the generated code (basically you'll
register each prop indiviaually using TopicUtils)
As for your stack
trace....Please send the stack trace and we'll read it and try to figure out why
you are getting it...
-Sal
From: Srinivasan, Latha
Sent: Wednesday, April 20, 2005 4:19 PM
To: [email protected]
Subject: Example implementations of Subscribe and GetCurrentMessage operations
Hi,
I
implemented a web service with resource prop. elements and some custom
operations. I want prop change notifications to be sent for all/some resource
prop. changes. I followed the filesystem example and created the relevant
operations and resource props for NotificationProducer. However, on sending
"subscribe" and "getcurrentmessage" soap messages to the deployed service, I get
exceptions and the stack trace doesn't even touch my code.
I am
assuming I need to write some more code to get subscribe and getcurrentmessage
to work currently. However, the filesystem example that's included with the
distribution doesn't provide any clues about how to go about doing this. Can
someone point me to some examples that I could look at to see how its done?
Ideally, I would like to see a sample that I can test before I start making
changes to my code.
Appreciate the help,
Latha
