sling-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] [sling-org-apache-sling-jcr-contentloader] ncautotest commented on issue #2: SLING-8375 - Allow import if data contains protected properties
Date Thu, 16 May 2019 15:33:48 GMT
ncautotest commented on issue #2: SLING-8375 - Allow import if data contains protected properties
URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/2#issuecomment-493118033
 
 
   @rombert: Using `javax.jcr.nodetype.ItemDefinition.isProtected()` would definitely be a
better way, but the data feeding into `org.apache.sling.jcr.contentloader.internal.DefaultContentCreator`
is just strings/string arrays coming from an external source. In order to have a `javax.jcr.Node`
instance the property would have to be set on a node and that throws a `ConstraintViolationException`.
Or is there by chance a  way to create a detached Node or something like that just in order
to figure out if the property is protected? 

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

Mime
View raw message