Using VLT to import a SysView XML document | Community
Skip to main content
A
Anonymous
October 16, 2015
Solved

Using VLT to import a SysView XML document

  • October 16, 2015
  • 4 replies
  • 862 views

Using the VLT import command:
    import -v|-s|--sysview <uri> <local-path> <jcr-path>
e.g.:
    vlt --log-level ERROR import -v --sysview <uri> sysview.xml /content/import-test/sysview
I can import a SysView doc and mount the nodes it contains at the correct point.

But if I re-run the import I just get the error:

[ERROR] import: javax.jcr.ItemExistsException: /content/import-test/sysview/<subnode_name>

which surprises me.

- Will the SysView import only import into empty structures?
- Is there any way of overwriting with the SysView?


And, whilst on the subject of SysView
- Why doesn't VLT have a SysView export function?

Thanks for your help.

 

EDIT: everyone's gone very quiet: is there no solution?

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by

Sorry to say this, but this is NOT a solution to the problem.

The task is not just to stick some arbitrary file into CQ, but to import and integrate a node structure using sysview serialized XML via VLT (the method proposed in the Adobe docs.).

I created a workaround for the initial problem by posting a cURL delete command of the root node before I installed the structure. Inelegant, but it works, which is the main thing. It is not a solution though.

Perhaps we can just accept a 'that's how it is' answer: VLT import will not delete the root node of an existing structure.

 

On the further point of sysview export, I used cURL to post to a customized service that downloads the serialization. Again, not elegant, but it works.

Thanks for your efforts

4 replies

A
Anonymous
October 16, 2015

Quick supplementary question on the same subject:

Can the .content.xml files in the vault also be in system view format?

This doesn't work for me.

J
Adobe Employee
JustinEd3Adobe Employee
Adobe Employee
October 16, 2015

Hi,

Sorry I missed this thread the first go-around. The import command in vlt uses the Workspace.import() method defined in the JCR specification. As you can see here: http://www.day.com/maven/jsr170/javadocs/jcr-2.0/javax/jcr/Workspace.html#importXML(java.lang.String, java.io.InputStream, int) the behavior when the path already exists is to throw an exception.

I don't know why SysView export isn't available; probably because no one has ever asked for it smiley. Would suggest you create a JIRA issue here: https://issues.apache.org/jira/browse/JCRVLT

Regards,

Justin

smacdonald2008
smacdonald2008
Level 10
October 16, 2015

Old thread - however to import files into AEM (it does not matter the type JS,CSS, XML), you can write a custom app/service. See this community article: 
http://helpx.adobe.com/experience-manager/using/post_files.html

A
Anonymous
Accepted solution
October 16, 2015

Sorry to say this, but this is NOT a solution to the problem.

The task is not just to stick some arbitrary file into CQ, but to import and integrate a node structure using sysview serialized XML via VLT (the method proposed in the Adobe docs.).

I created a workaround for the initial problem by posting a cURL delete command of the root node before I installed the structure. Inelegant, but it works, which is the main thing. It is not a solution though.

Perhaps we can just accept a 'that's how it is' answer: VLT import will not delete the root node of an existing structure.

 

On the further point of sysview export, I used cURL to post to a customized service that downloads the serialization. Again, not elegant, but it works.

Thanks for your efforts

Terms & ConditionsAccessibility statement

Loading footer...