[
https://issues.jboss.org/browse/JBIDE-12549?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-12549:
-------------------------------------
also in this commit is limiting direct access to the sets and arrays of the model. this
prevents random dialogs from clearing the model and it forces a workflow.
I've switched the apis to use arrays instead to help find all cases where such things
were happening. It happened more often than expected and I was nervous about leaving any
assumed direct access if i returned a clone of the set. Dialogs might think they were
modifying the real model and in fact werent. this switch seems to have helped.
Change api for runtime detectors to hide access to setters except by
framework
------------------------------------------------------------------------------
Key: JBIDE-12549
URL:
https://issues.jboss.org/browse/JBIDE-12549
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: runtime detection
Affects Versions: 4.0.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.0.0.Alpha2
The API for the runtime detectors is too liberal and allows access to things that should
be handled by the framework alone. Things such as setting priority, name, id, preference
id, etc.
Also, several of the classes should be internal and not exposed. The model to do so is to
have a framework class in charge of such extension point attributes and have a delegate
able to fulfill the requests for the methods that matter.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira