jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "angela (JIRA)" <j...@apache.org>
Subject [jira] Created: (JCR-114) Suggestion regarding NodeImpl and PropertyImpl in jackrabbit.core
Date Fri, 22 Apr 2005 10:48:35 GMT
Suggestion regarding NodeImpl and PropertyImpl in jackrabbit.core

         Key: JCR-114
         URL: http://issues.apache.org/jira/browse/JCR-114
     Project: Jackrabbit
        Type: Improvement
  Components: API  
    Reporter: angela
    Priority: Trivial

Both NodeImpl and PropertyImpl contain in their respective setProperty/setValue (respectively)
initial validation checks, that is indentical across the various
variants of each and could possibly in either case be place in a separate method.

in NodeImpl.setProperty (also: addMixin, removeMixin, orderBefore):

- sanityCheck
- is-parent-checked-out
- is-not-protected (missing for setProperty ???)
- is-parent-not-locked

in PropertyImpl.setValue:

- sanityCheck
- is-parent-checked-out
- is-not-protected 
- is-value-compatible-with-multivalue-definition (NOTE: check opposite for setting single
  or multiple values)
- is-parent-not-locked

Second, i'm never sure, in which case ChildNode, ChildProperty is prefered 
over Node/Property (as present in the jcr api)...


This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message