>> On Wed, Jun 9, 2010 at 2:40 PM, Vidar Ramdal <[email protected]> wrote: >>> With Jackrabbit 1.6.2, however, this fails: >>> javax.jcr.nodetype.ConstraintViolationException: no matching property >>> definition found for {http://www.jcp.org/jcr/1.0}lastModified >>> [...] >>> Is this a bug, or intentional?
> On Wed, Jun 9, 2010 at 2:47 PM, Jukka Zitting <[email protected]> wrote: >> This looks like a side-effect of JCR-2170. Can you file a bug for this >> so we can fix it for 1.6.3? On Wed, Jun 9, 2010 at 3:08 PM, Vidar Ramdal <[email protected]> wrote: > Done => https://issues.apache.org/jira/browse/JCR-2652 I think I might have found something. In o.a.j.core.ItemManager#225, NodeImpl.getApplicablePropertyDefinition is called with exactTypeMatch=true. This will not work when there is no, er, exact match. Switching the flag to true fixes the issue. Does this sound reasonable? I have run the tests in jackrabbit-core, but I can't get them all to pass at the moment - something in my local maven repo is messed up, probably. But then, the same number of tests fail with or without the fix. I'll prepare a patch and attach it to the JIRA task [1] - please review. [1] https://issues.apache.org/jira/browse/JCR-2652 -- Vidar S. Ramdal <[email protected]> - http://www.idium.no Sommerrogata 13-15, N-0255 Oslo, Norway + 47 22 00 84 00 / +47 22 00 84 76 Quando omni flunkus moritatus!
