Expand my Community achievements bar.

Form Fails when uploading via webdav


Level 5

hey guys,

In Forms&Documents I created a new folder and uploaded my XDP template. That works fine.

But when I connect via webdav and upload the XDP file in the same folder structure (/content/dam/formsanddocuments/MYFOLDER) it doesn't show in the web interface.

I took both log files and the only difference I see when uploading via web interface versus webdav is this (logged when uploading via web, but nothing is shown when uploading via webdav):

16.09.2015 17:28:53.809 *INFO* [0:0:0:0:0:0:0:1 [1442435333806] POST /libs/fd/fm/content/manage.json HTTP/1.1] com.adobe.livecycle.formsmanagement.servlets.FormsManagementServlet Uploading File ( KIT-4008-174E.xdp ) at : /content/dam/formsanddocuments/myfolder 16.09.2015 17:28:53.820 *INFO* [0:0:0:0:0:0:0:1 [1442435333806] POST /libs/fd/fm/content/manage.json HTTP/1.1] com.adobe.livecycle.formsmanagement.servlets.FormsManagementServlet No node exists at path : /content/dam/formsanddocuments/myfolder/myfile.xdp 16.09.2015 17:29:01.813 *INFO* [0:0:0:0:0:0:0:1 [1442435341807] POST /libs/fd/fm/content/manage.json HTTP/1.1] com.adobe.livecycle.formsmanagement.servlets.FormsManagementServlet No node exists at path : /content/dam/formsanddocuments/myfolder/myfile.xdp 16.09.2015 17:29:01.814 *INFO* [0:0:0:0:0:0:0:1 [1442435341807] POST /libs/fd/fm/content/manage.json HTTP/1.1] com.adobe.livecycle.formsmanagement.servlets.FormsManagementServlet Creating new LC Form 16.09.2015 17:29:01.892 *INFO* [0:0:0:0:0:0:0:1 [1442435341807] POST /libs/fd/fm/content/manage.json HTTP/1.1] com.adobe.livecycle.formsmanagement.service.impl.FormsManagementServiceImpl Deleting archive /content/dam/formsanddocuments/temp_archive_storage/tempArchive_686800377089364 16.09.2015 17:29:01.893 *INFO* [Thread-63] com.adobe.livecycle.formsmanagement.listeners.FormSynchronizer Synchronizing request{name=KIT-4008-174E.xdp, path=/content/dam/formsanddocuments/myfolder/myfile.xdp}


So how can get it to work?


2 Replies


Level 2


When you upload an XDP template through Forms&Documents UI, it carries out a couple of processes in the background. This includes creating a DAM Asset structure for the form, adding an identifier for the form type (XDP) and extracting metadata from the form content bytes. So, in short a form in AEM Forms is not simply bytes stored in the repository but an asset with a defined structure and certain additional information stored along with the bytes.

So, when you upload the XDP file via webdav, I guess it would not be hitting our REST endpoint and so the processes will not run. The final structure of the XDP file would not be the same as that expected by the AEM Forms UI. We do not really support uploading form bytes from an external source outside AEM Forms&Documents UI.

Is there any specific reason you wish to upload the form via webdav?




Level 5

Hi Anshika, thanks for the reply.

In a team of 20 people working with XDP templates/fragments, I'm thinking in how they can work together. I thought if they were connected to the same webdav folder would be the way.

Is there a best practice so they can work smoothly in many XDP files, uploading to the author with version control?