FUSETOOLS-1585 - beginnings of adding bean support (#880)
*
FUSETOOLS-1585 - beginnings of adding bean support
-- adding to Global Configuration page as an "Add" possibility
-- started work on the Bean wizard
-- started on property page for bean properties
-- have basic bean property page working
-- added ID validation for global configuration elements
-- added browse button for bean class in wizard page
-- added class name validation in wizard page
-- added class name validation on property page
-- added class browse button on property page
-- added method browse button on property page
-- added method validation on property page
-- added first cut of property and argument table controls to wizard
-- added support for defining arguments and properties in config
-- some Sonar cleanup
-- added edit buttons to property & argument tables
-- more sonar cleanup
-- addressing comments from Aurelien and more cleanup
-- additional sonar cleanup of lambdas and an icon issue
-- more sonar cleanup and addition of property name uniqueness
validation plus bean id uniqueness validation in property page
-- even more sonar suggested fixes
-- addressing a NPE and some other suggestions made by Aurelien
-- more sonar fixes
-- added edit functionality for properties and arguments
-- added a few sonar & Aurelien-requested changes
-- fixed issue with xml not being added/updated correctly
-- fixed some property name validation issues
-- fixed issue with adding wrong constructor argument tag name to
blueprint
-- further correction to method used to find namespace for blueprint
-- adding beginnings of IT test
-- updated test so it works and refactored some code for easier testing
-- beefed up test to cover basic use cases and blueprint vs. spring
testing
-- added additional tests for creation and editing of beans
-- did a little test refactoring
-- added factory-method/factory-bean functionality to property page and
tests for it
-- added ability to create new class from bean wizards and property page
*
FUSETOOLS-1585 - set new java class wizard to not auto-open
Discovered that the new java class wizard opens the new class for
editing immediately after clicking Finish. For this case, we don't want
it to open, since focus would then shift from the Camel Editor.
*
FUSETOOLS-1585 - addressing some of Aurelien's feedback,
adding a new test, and correcting a couple of labels
*
FUSETOOLS-1585 - moving some XML attribute setting/getting code back to
the CamelBean model object. Adding a test to ensure that it can be
loaded properly and changed via the CamelBean object.
*
FUSETOOLS-1585 - adding more tests and functionality to CamelBean
*
FUSETOOLS-1585 - small code improvements
* Fixed issue with refresh
* Fixing issue where src/main/java not created yet
*
FUSETOOLS-1585 - Factorize code and leverage java 8 streams
* Attempting to fix test issues with Shells
* Updates to PropertyInputDialogTest as suggested by @apupier
* Update to fix one issue
* fix the swt / cocoa lib failures from CI
* fixes model problem
* Specialize bean extension to not clash with SAP
* Addressing an issue found by the Core model test
-- also includes feedback from Aurelien on a couple of code tweaks
* Addressing more comments - test for SAP extension, code cleanup
* Externalizing strings for the Bean work
* Fixes for next round of comments
* Updates to allow specialization of Globel elements and a sonar fix
*
FUSETOOLS-1585 - addressed more feedback
- factorized code requested in AdvancedBeanPropertiesSection and
AdvancedEndpointPropertiesSection
- updated developer name in javadocs to be consistent
- fixed validation issues with Property and Argument dialogs so
validation prevents OK button from being active
- removed code around potential WRONG_DOCUMENT_ERR since the last round
of model updates seems to have removed the necessity
*
FUSETOOLS-1585 - Avoid having two times the same WizardPage
Before the pages on the wizard are added twice in
org.fusesource.ide.camel.editor.globalconfiguration.beans.BeanConfigUtil.handleNewClassWizard(IProject,
Shell) , there is a addPages() called which is also called when
wizard.open() is called which was causing that nothing happened when
clicking "Next"
Now, it is called a single time. No next button is displayed.
