dcorking / google-wave-resources

Automatically exported from code.google.com/p/google-wave-resources
0 stars 0 forks source link

Bug: wave.wavelet.modifyParticipantRole fails on wavelets created with active api and submitted with passive api #755

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago
Steps to re-create the issue:
 0. react to an event
 1. create a wavelet with the active api 
    - newWave(domain, participants, msg, proxyForId, rpcServerUrl)
 2. modify the role of a participant in the wavelet created in 1
 3. set the title of the wavelet created in 1
 4. submit the created wavelet with the passive api

Included is a java robot which performs these steps and a log file of the 
result. 

The log file shows the participant role change to be submitted to the 
server but the change never gets reflected in the wave. Neither does the 
result of setting the title.

This only applies when submitting the created wavelet with the passive api. 
And it only applies when the wavelet has been created with newWave(domain, 
participants, msg, proxyForId, rpcServerUrl). The other newWave(...) 
methods work as expected.  So does submitting the created wavelet with the 
active api. (see issue:753)

Original issue reported on code.google.com by peter.o....@gmail.com on 6 May 2010 at 10:26

Attachments:

GoogleCodeExporter commented 8 years ago
Hmm, we're looking into this.

It may be possible that you registered your consumer key for 
one-360@appspot.com, so 
the new wave will be created by that participant id, but then, the robot is 
responding 
to events for 9.latest.one-360@appspot.com, which can't modify the participant 
role.

What app ID did you register the consumer key for?

Original comment by pamela.fox on 7 May 2010 at 1:20

GoogleCodeExporter commented 8 years ago
I did register the consumer key for one-360@appspot.com. If that explains the 
failure 
it doesn't appear to explain why it doesn't fail when creating the wavelet with 
the 
other newWave(...) methods?

Original comment by peter.o....@gmail.com on 7 May 2010 at 7:37

GoogleCodeExporter commented 8 years ago
I tested running robot with the version I registered the consumer key for. The 
results 
were the same. Included are the code I run and the log output.

Original comment by peter.o....@gmail.com on 7 May 2010 at 8:26

Attachments:

GoogleCodeExporter commented 8 years ago
I suddenly realized that it was an issue with my appengine application and not 
with 
wave. Terribly sorry for the hassle I caused. For some reason the wavelet 
created with 
newWave(domain, participants, msg, proxyForId, rpcServerUrl) got dispatched to 
a 
version of the robot which I had deleted!? I deployed to a fresh application id 
and 
everything worked as it should.

With apologies,
Peter

Original comment by peter.o....@gmail.com on 7 May 2010 at 9:34

GoogleCodeExporter commented 8 years ago
Okay, thanks for updating.

Original comment by pamela.fox on 7 May 2010 at 10:08