The answer used to be as in this recipe: http://groups.google.com/group/google-wave-api/browse_thread/thread/670ced3f13765e4d/f3b3a2a18ffffbd1?hl=en&#f3b3a2a18ffffbd1 but as noted later in that thread you have to specify the DOCUMENT_CHANGED event in the capabilities.xml file. This seems to be and on and off problem as I think I have received unsolicited DOCUMENT_CHANGED events between then (8dec) and now. Either way, at the moment they are not sent. However, you will receive the "_new_ids_" data document with the next event the robot receives (maybe not all events but at least with wavelet_blip_created, form_button_clicked and blip_submitted).
Maybe somebody could shed some light on this issue? Receiving the unsolicited DOCUMENT_CHANGED event is a very tractable solution from a robot programmers perspective. Specifying it in the capabilities.xml file is not, unless you want to listen to that event for other reasons. ~Peter On Feb 14, 8:28 am, Karan <karan.guj...@gmail.com> wrote: > I have a robot that can create a new wave based on some conditions. My > problem is that I am unable to programatically get the wave id of this > newly created wave. I'm writing the robot in java, and here are the > things I've tried. > > 1. Call getWaveId on the new wave. This returns a TBD..... string. > 2. Give a callback data document as part of the create method. The > callback data document is not present in the data document map. > 3. Assuming the values would be updated later, I wrote a cron job (app > engine) to get the wave id from the wavelet object. The wavelet object > is not updated with the wave id. > > Am I missing something obvious? > > Thanks, > Karan -- You received this message because you are subscribed to the Google Groups "Google Wave API" group. To post to this group, send email to google-wave-...@googlegroups.com. To unsubscribe from this group, send email to google-wave-api+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
