[
https://issues.apache.org/jira/browse/GRFT-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Christophe Lombart resolved GRFT-84.
------------------------------------
Resolution: Fixed
Fix Version/s: ocm-1.0
>From now, the ocm tools is supporting all kind of jcr properties. see the
>unit test : PersistenceManagerJcrPropertyTest.java
> ObjectConverterImpl wrong behavior when manipulating autoCreate and protected
> properties
> ----------------------------------------------------------------------------------------
>
> Key: GRFT-84
> URL: https://issues.apache.org/jira/browse/GRFT-84
> Project: Graffito
> Issue Type: Bug
> Components: JCR-Mapping
> Affects Versions: 1.0-a1-dev
> Reporter: Alexandru Popescu
> Assigned To: Christophe Lombart
> Priority: Critical
> Fix For: ocm-1.0
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
