Personally, I am opposed to making simple things like this overly
complicated. It is unlikely the Java collections API will change enough
to warrant a factory for every collection type.
Javolution was used in Java 1.4 to reduce the latency caused by garbage
collection. That is not a problem with JREs >= 1.5, so we don't need the
library any more.
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 3/28/2015 10:01 AM, Taher Alkhateeb wrote:
Hi All,
The move from javolution to the collections API built in to java proves to be painful. To
avoid such things in the future and to reduce the "new" keyword clutter in the
code I suggest we create factories for all collections. This way we we can also enhance
the collections in the future with any ofbiz specific code. This is also a best practice
in terms of design patterns.
I would like to have opinions on whether this is a wanted / acceptable feature
so I can create a JIRA accordingly. Your opinions are appreciated.
Taher Alkhateeb.
