You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Stefan Seifert (JIRA)" <ji...@apache.org> on 2015/01/14 12:38:34 UTC

[jira] [Commented] (SLING-4267) Json content import does not work for the JCR_JACKRABBIT resource resolver type

    [ https://issues.apache.org/jira/browse/SLING-4267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14276815#comment-14276815 ] 

Stefan Seifert commented on SLING-4267:
---------------------------------------

no, it is indeed not intended to import binary data via JSON, this is always done via separate methods of the content loader because the binary data itself is not referenced in the JSON file.

in rev. 1651623 i've addes some more property names to the "ignore" list of the content loader that are managed by JCR internally - and ":jcr:data" as well.

with this the unit tests are running save one: the testDamAssetMetadata test failes, because the node with primary type "nt:resource" cannot be stored. the :jcr:data property is omitted as expected, but JCR does not allow saving a "nt:resource" node without binary data in it. but we cannot import it because we do not have it at this moment how to solve?

> Json content import does not work for the JCR_JACKRABBIT resource resolver type
> -------------------------------------------------------------------------------
>
>                 Key: SLING-4267
>                 URL: https://issues.apache.org/jira/browse/SLING-4267
>             Project: Sling
>          Issue Type: Bug
>          Components: Testing
>    Affects Versions: Testing Sling Mock Jackrabbit 0.1.0
>            Reporter: Robert Munteanu
>             Fix For: Testing Sling Mock Jackrabbit 0.2.0
>
>         Attachments: SLING-4267-1.diff
>
>
> The tests complain that {noformat}app: is not a registered namespace prefix.{noformat}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)