You are correct. You should see notifications.
I looked at the source code for the WsdmExplorer class and found this line right after the subscribe request...
   
    subscription.pauseSubscription();
 
Someone, perhaps myself, put this line in for some purpose but the result is that any subscription requested get paused as soon as it is made. I have checked in this change so you should pick it up and try again.
 
Assumeing that you still have a problem, I would set a stop in WsdmExplorer Line 123 to get a look at that the contents of your notification looks like. If you never reach that point then look at NotificationConsumerImp line 239 which attempts to parse the message and has accesss to the raw notification tests.
 
Another option would be to increase the log level of the whole application by adding a copy of the log4j.properties file to the top of your classpath and change all occurances of the word INFO with DEBUG. This will considerably increase the amount of output that the WsdmExplorer will generate. In will print the received notification text out as a DEBUG log entry.
 
-Bill



From: Lombrera Lombrera [mailto:[EMAIL PROTECTED]
Sent: Monday, October 24, 2005 8:47 AM
To: Reichardt, William
Subject: Help with WSDM Client

Hi William, thanks for your previous reply.
Now I get the Client working. The problem I had before was with the xmlbeans*.jar.
 
Now... I got another problem.
When I run the WsdmExplorer class, the "get" and "set" works fine, but the "Listen" is not working as I think it should.
 
My Listen is to:
"http://localhost:8080/muse/filesystem.xml", "listen", "{http://ws.apache.org/resource/example/filesystem}Comment"

The output in the console is this:

Oct 20, 2005 3:10:51 PM org.apache.ws.client.muse.client.impl.notification.NotificationConsumerImpl listenerServiceLoop

INFO: Listener Going into accepting state

Now listening on http://notebook:8089 to Topic {http://ws.apache.org/resource/example/filesystem}Comment

Hit any key to destroy your subscription.

Until then all notifications received will be written here.

 
---  Here I do a set (using ant in the command prompt) and the output in the console is ---:

Oct 20, 2005 3:13:58 PM org.apache.ws.client.muse.client.impl.notification.NotificationConsumerImpl listenerServiceLoop

INFO: This notification socket has been closed.

Oct 20, 2005 3:13:58 PM org.apache.ws.client.muse.client.impl.notification.NotificationConsumerImpl workerServiceLoop

INFO: Processing received notification.

Oct 20, 2005 3:13:58 PM org.apache.ws.client.muse.client.impl.notification.NotificationConsumerImpl listenerServiceLoop

INFO: Notification Listening restarting.

Oct 20, 2005 3:13:58 PM org.apache.ws.client.muse.client.impl.notification.NotificationConsumerImpl listenerServiceLoop

INFO: Listener Going into accepting state

 
I think it should have printed out all the notification message, right?
What probably am I doing wrong? 
 
Thanks again,
Lombrera.
------------------------------------


Promoção Yahoo! Acesso Grátis: a cada hora navegada você acumula cupons e concorre a mais de 500 prêmios! Participe!

Reply via email to