In the first bit of code, you never set the data document, so I would
expect it to be null. Why were you expecting it to give a value?
(Maybe I'm missing something).
- pamela
Blip appendBlip(java.lang.String writeBackDataDocument)
Creates a new blip and appends it to the end of the wavelet. The
resulting blip id of the new blip will be stored in a data document on
the wavelet whose event was being processed at the time the blip was
created.
Parameters:
writeBackDataDocument - The name of the data document to
create.
Returns:
the newly created blip.
there is a chance i'm the one missing something here :)
thanks again, and happy new year.
On Dec 31, 1:13 am, "pamela (Google employee)" <pamela....@gmail.com>
wrote:
The API doesn't know the actual ID of the blip until after the
operations are sent to the server, and just gives you a temporary ID.
The server then puts a datadocument of the new ID in the wavelet, so
that you can retrieve it after a DOCUMENT_CHANGED event.
I have used a similar technique to find out the ID of a new wave (see:
http://wave-samples-gallery.appspot.com/about_app?app_id=60017), I
haven't used it to find out the ID of a new blip. I imagine it is the
same technique.
- pamela
> --
>
> 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-...@googlegroups.com.
> To unsubscribe from this group, send email to google-wave-a...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/google-wave-api?hl=en.
>
>
>