Additional information, my dev repository is one converted from a jackrabbit repository. Can the warning be triggered not by the node that's being added, but by some nodes in the converted repository not being unique?
On 29 July 2014 13:19, Torgeir Veimo <[email protected]> wrote: > I am getting a lot of these, > > javax.jcr.nodetype.ConstraintViolationException: OakConstraint0030: > Uniqueness constraint violated for key > 42cd9011-84a8-485f-b723-435439ddcc71 > > It seems to happen on session.save(), having just created a node of > type nt:unstructured, with a mixing node type which inherits > mix:referenceable. > > I can't seem to see any other pattern. Is there anything in particular > that could cause this, with code that worked ok with jackrabbit 2.8? > > This is with oak 1.0.3, but I've seen it on 1.0.1 and 1.0.2 as well. > -- > -Tor -- -Tor
