sco0ter / Babbler / issues / #84 - ExternalComponent never fire RECONNECTION_SUCCEEDED event? — Bitbucket

Issue #84 closed

Vitaly Takmazov created an issue 2016-08-03

I'm using the very basic ExternalComponent with very basic ConnectionListener (as shown in "Dis- and Reconnection" article). I'm receiving DISCONNECTED and RECONNECTION_PENDING events, but neved got SUCCEEDED event (but I see it is connected to server). What I am missing? I can provide example code, if any.

Comments (5)

Christian Schudt repo owner
- changed status to resolved
Make sure RECONNECTION_SUCCEEDED event is trigger for external components.

Fixes issue ~~#84~~

→ <<cset b2bc9b86d875>>
- 2016-08-03T18:13:25+00:00
Christian Schudt repo owner
You are right. Unfortunately, it's a bug.
- 2016-08-03T18:13:55+00:00
Christian Schudt repo owner
Make sure RECONNECTION_SUCCEEDED event is trigger for external components.

Fixes issue ~~#84~~

→ <<cset b38b54a6a791>>
- 2016-08-03T18:42:52+00:00
Christian Schudt repo owner
Fixed with version 0.7.1
- 2016-08-11T11:04:50+00:00
Christian Schudt repo owner
- changed status to closed
- 2018-07-17T08:05:58+00:00
Log in to comment

Assignee: –

Type: bug

Priority: major

Status: closed

Version: –

Votes: 0

Watchers: 1

Jira: the preferred issue tracker for Bitbucket. Join the team!