On 9 February 2017 at 13:38, Stian Soiland-Reyes wrote:
> Peter Ansell raised a valid question about why in Commons RDF I made the
> RDFParser interface as an immutable factory-like builder pattern.
>
> https://commons.apache.org/proper/commons-rdf/apidocs/org/apache/commons/rdf/experimental/RDFPa
The Apache Commons Team is pleased to announce the availability of:
Apache Commons JCS 2.1
Apache Commons JCS is a distributed, versatile caching system.
The release notes can be reviewed at:
http://www.apache.org/dist/commons/jcs/RELEASE-NOTES.txt
Distribution packages can be downloaded from:
The Apache Commons team is happy to announce the release of Commons
Configuration 2.1.1!
The Commons Configuration software library provides a generic configuration
interface which enables a Java application to read configuration data from a
variety of sources. Commons Configuration provides ty
Come to think of it, clone() is going to make a shallow copy anyways, so
any RDFParser fields here wouldn't get copied between clones, just
references.
On 9 February 2017 at 03:44, sebb wrote:
> I've not looked at the code itself yet, but AFAIK clone() is not
> sufficient to ensure thread-safety
I've not looked at the code itself yet, but AFAIK clone() is not
sufficient to ensure thread-safety of a mutable object.
This is a consequence of the Java memory model, which allows items to
be cached locally.
Simply put, safe publication of values requires that the reader of a
field synchronise o
