Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MODE-1138 Improved error message when value violates property definition constraint #62

Merged
merged 3 commits into from Apr 8, 2011

Conversation

rhauch
Copy link
Contributor

@rhauch rhauch commented Apr 8, 2011

Improved the error message when a property definition could not be found because only the constraint is violated. The message is of the form:

The '{0}' property value '{1}' on node '{2}' does not satisfy the constraints of the '{3}' property definition on the '{4}' node type, and no other property definition is valid.

The message is slightly different for multi-valued properties, for REFERENCE properties, and WEAKREFERENCE properties.

All unit and integration tests pass with these changes.

…e versionable nodes in history

As noted in the JIRA issue, the JcrVersionManager.checkin(...) method calls the versionNodeAt(...) recursive method, which copies the versionable state into the new version in version history. This method should *not* be walking children when the child is 'mix:versionable' and has an OPV on the child node definition of VERSION.

This change simply implements this behavior by returning from the method rather than breaking (the children are walked after the break).

All unit and integration tests pass with this minor change.
@rhauch rhauch merged commit bd6e583 into ModeShape:master Apr 8, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants