[ 
https://issues.apache.org/jira/browse/WAVE-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231065#comment-13231065
 ] 

Yuri Zelikov commented on WAVE-339:
-----------------------------------

I can't reproduce the issue on waveinabox.net.
For example, I can create a wave and then use the "waveaids" robot to append 
some text with GET to following URL
http://waveaids.appspot.com/process?message=some+message&waveId=w%2B_cYBfSH0WQA
Can it be that it happens on your modified instance since you don't initialize 
all waves on server startup?

Anyway, it seems like the issue is caused by waveletUpdate events being 
dispatched to ClientFrontendImpl even for waves that were not open by any 
webclient user. I think it can be solved by adding a test in ClientFrontendImpl 
if the update is for a wave that was initialized, and if not - skipping any 
further handling of this event.
                
> Update wave from robot causes exception and corrupt WaveletInfo
> ---------------------------------------------------------------
>
>                 Key: WAVE-339
>                 URL: https://issues.apache.org/jira/browse/WAVE-339
>             Project: Wave
>          Issue Type: Bug
>            Reporter: Andrew Kaplanov
>            Assignee: Yuri Zelikov
>
> 1) Start Wiab server.
> 2) Register robot.
> 3) Subscribe robot to one of your waves.
> 4) Logout  from client.
> 5) Stop Wiab server. 
> 4) Make and run robot with following code:
> String waveId = your existing wave
> WaveService service = new WaveService();
> service.setupOAuth(...);
> Wavelet wavelet = service.fetchWavelet(WaveId.deserialise(waveId),
>     WaveletId.of(DOMAIN, IdUtil.CONVERSATION_ROOT_WAVELET), URL);
> wavelet.getRootBlip().append("something text");
> service.submit(wavelet, URL);
> 5) Login from client and select wave. You will see an error "No conversations 
> in this wave".
> 6) In the log file you will see an error "Expected deltas starting at version 
> ..., got ..."

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to