Maris, did you ever get your issue solved? I'm having a similar issue: My capabilities.xml file is getting cached, and even though I change the version number in it, adding or removing event handlers from it has no effect. So, as an example, I started with registering the document_changed handler, pushed it to appengine to test it, and it works fine. Then I added wavelet_participants_changed, and up'd the version number in capabilities.xml. If I go to capabilities.xml, I can see that my new version number is there, and the new event handler is there. However, I have my robot littered with loggers, and the wavelet_participants_changed event is never firing. In the logs, I do see that capabilities.xml is rendering when I add my robot to a wave, so the wave server does seem to be checking my capabilities.xml, just never using it...
Also, if I wait a day or two, and never use that robot, then my new event handler starts working. I'm not sure the exact amount of time, but at some point, it seems to fall out of cache, and the new capabilities get registered. Anybody have any ideas? Thanks! Jason On Aug 22, 10:24 pm, Van Riper <[email protected]> wrote: > On Fri, Aug 21, 2009 at 1:37 PM, Gmail<[email protected]> wrote: > > yes i have seen that blog :( but still nothing! > > but stll thanks! > > Maris > > So, you did follow the recommendation to change theversionin the > capabilities.xml file whenever you make changes to the contents? If > not, you should give that a try and be sure to check your logs for > anything peculiar. > > -Van --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en -~----------~----~----~----~------~----~------~--~---
