Matthew, can you give some more context for this request? StringBuilder may be a better choice than StringBuffer, but is there an issue you are trying to address? Do you use Serp directly? Or, are you using it as part of another project (ie. OpenJPA)?
Serp is a mature utility that does not see a lot of development activity. Actually, this is the first Bug report I've seen since I started to monitor the Serp project several years ago... Any additional justification for this defect would be appreciated. Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
My interest is in OpenJPA, which uses Serp. I have been working on reducing the amount of BLOCKED threads and have been looking for unnecessary synchronization is occurring.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Matthew, can you give some more context for this request? StringBuilder may be a better choice than StringBuffer, but is there an issue you are trying to address? Do you use Serp directly? Or, are you using it as part of another project (ie. OpenJPA)?
Serp is a mature utility that does not see a lot of development activity. Actually, this is the first Bug report I've seen since I started to monitor the Serp project several years ago... Any additional justification for this defect would be appreciated. Thanks.
This isn't a bug per se, more of a tech debt issue. See the javadocs of StringBuilder for the justification:
http://docs.oracle.com/javase/1.5.0/docs/api/java/lang/StringBuilder.html
My interest is in OpenJPA, which uses Serp. I have been working on reducing the amount of BLOCKED threads and have been looking for unnecessary synchronization is occurring.
Delivered to Serp trunk.