[
https://issues.jboss.org/browse/JBIDE-21449?page=com.atlassian.jira.plugi...
]
Jeff Cantrill commented on JBIDE-21449:
---------------------------------------
[~mlabuda] From your perspective, I'm not sure this is a valid test since the UI
should be unchanged. I noticed it by:
Connect to a server and expand a project (starts watch)
Add a service to the project if one does not exist
Set a break point in the OpenShiftExplorerContentProvider#propertyChange method
Edit the service and add a label. Note single callback
Wait for the WatchManager to be disconnected and for it to reconnect itself
Edit the service again by removing the label.
Assert: Callback occurs only once (previously received callbacks equal to every
WatchManager restart)
WatchManager makes multiple callbacks for same event
----------------------------------------------------
Key: JBIDE-21449
URL:
https://issues.jboss.org/browse/JBIDE-21449
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.1.Beta1
Reporter: Jeff Cantrill
Assignee: Jeff Cantrill
Priority: Blocker
Fix For: 4.3.1.CR1
There is an issue in either the WatchClient or the the dependent functionality of the the
openshift-rest-client where a new listener is registered when the watch restarts from a
timeout. Listeners should only be able registered once
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)