Community
Participate
Working Groups
StringBuffer is synchronized, StringBuilder is not, therefore replace all usage of StringBuffer by StringBuilder unless there is a specific need for synchronization.
Numerous local changes in examples/tests committed to bug 318092 branch, whih will be merged to master once I can build on Hudson again. Additional changes to core/impact plugins await review in (the last commit to) bug/364806. A couple of minor APIs use StringBuffer. These cannot be changed, but could be duplicated; I don't think the duplication is justified. Further changes in auto-generated code await a template change for bug 367705.
The branch for this bug mixes changes regarding the obvious StringBuffer-->StringBuilder with changes regarding the way how delegates are resolved and how their URIs are being handled. I don't see the connection with the StringBuilder changes and suggest to move the delegate stuff to a separate bug / branch and keep this branch's changes limited to the subject of this bug.
Sorry, my bad; had'n merged the latest origin/master into my local master... Now reviewing the right diff. All I see in the core bundles are StringBuffer-->StringBuilder diffs. +1 for merge to master.
Pushed to master for M5.
CLOSED after a year in the RESOLVED state.