[GitHub] [sling-org-apache-sling-jcr-contentloader] ncautotest opened a new pull request #2: SLING-8375 - Allow import if data contains protected properties

[GitBox <gi...@apache.org>]

ncautotest opened a new pull request #2: SLING-8375 - Allow import if data contains protected properties
URL: https://github.com/apache/sling-org-apache-sling-jcr-contentloader/pull/2
 
 
   - possibly the try/catch solution is a bit of a brute-force approach and a better solution might exist which would use the JCR API. Yet given that custom node definitions can be used I consider that it's better to handle the exceptions and proceeed rather than hard-coding a list of property names which don't necessarily belong in the sling namespace and might be produce-specific i.e. `cq:xyz`

----------------------------------------------------------------
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