different places!
Taher Alkhateeb
- Original Message -
From: "Adrian Crum"
To: dev@ofbiz.apache.org
Sent: Saturday, 28 March, 2015 1:40:31 PM
Subject: Re: Proposal to introduce factory pattern to java collections
Personally, I am opposed to making simple things like this ov
least the best practices will be documented and
encapsulated in the factory.
Ron
Taher Alkhateeb
- Original Message -
From: "Adrian Crum"
To: dev@ofbiz.apache.org
Sent: Saturday, 28 March, 2015 1:40:31 PM
Subject: Re: Proposal to introduce factory pattern to java collections
eople using different implementations of the
interfaces in different places!
Taher Alkhateeb
- Original Message -
From: "Adrian Crum"
To: dev@ofbiz.apache.org
Sent: Saturday, 28 March, 2015 1:40:31 PM
Subject: Re: Proposal to introduce factory pattern to java collections
P
when
looking at the source code I see people using different implementations of the
interfaces in different places!
Taher Alkhateeb
- Original Message -
From: "Adrian Crum"
To: dev@ofbiz.apache.org
Sent: Saturday, 28 March, 2015 1:40:31 PM
Subject: Re: Proposal to in
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 wi
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
