[
http://issues.apache.org/jira/browse/GRFT-84?page=comments#action_12361742 ]
Alexandru Popescu commented on GRFT-84:
---------------------------------------
1/ autocreated properties
Yes the null value should be written, iif the property is not protected or required.
2/ protected properties
Good finding. My strategy would be: is the property configured (in the mapping) as protected: if yes ignore it. If not use the suggested canSetProperty and in case the return is false, throw an exception.
./alex
--
.w( the_mindstorm )p.
> ObjectConverterImpl wrong behavior when manipulating autoCreate and protected properties
> ----------------------------------------------------------------------------------------
>
> Key: GRFT-84
> URL:
http://issues.apache.org/jira/browse/GRFT-84> Project: Graffito
> Type: Bug
> Components: JCR-Mapping
> Versions: 1.0-a1-dev
> Reporter: Alexandru Popescu
> Priority: Critical
>
> 1/ autocreated properties
> When writting a property it ignores the autoCreated properties. But according to JSR-170 the
> autoCreated properties are writtable, so IMO these should not be ignored. The only requirement
> related to autoCreated properties is that they should have a default value, but this is required to
> be provided by the node definition.
> 2/ protected properties
> There is no check against the protected properties. According to JSR-170 these can be read,
> but cannot be write, so an attempt to write such a property should result in an exception. The
> current implementation relies on the repository to throw this exception, but IMO a better behavior
> would be not to attempt to write it.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
