renderPDFForm XDP and fragment strategy hepl

[jpadron_uy]

Hello

I'm using the Forms service, renderPDFForm(...)method to render XDP with FRAGMENTS and would like to know if it is possible to have one hand out of Adobe LC repository XDP Fomrs (accessed through http://.../myforms_01.xdp, etc) and within the Repository all fragments.

Is it possible? How would indicate the location of the fragments in the invocation renderPDFForms (...)? How should reference the fragments in XDP forms in Designer to work?

My idea was to generate locally a structure folders identical to Adobe LC repository, so that the relative path of the fragments matches the folder structure of the repository, but can not get to work, and I get the error:

09:35:40,077 WARN  [XMLFormService] ALC-XTG-102-001: [2672] Cannot resolve url: ROOT\MYAPP\FRAGMENTOS\MYAPP_FRAGMENTO_DE_CONTROL.xdp.

09:35:40,077 WARN  [XMLFormService] ALC-XTG-102-001: [2672] Bad value: 'ROOT\FORPDF\FRAGMENTOS\MYAPP_FRAGMENTO_DE_CONTROL.xdp#som($template.form1.control)' of the 'usehref' attribute of 'subform' element ''. Default will be usedinstead.

09:35:40,077 WARN  [XMLFormService] ALC-XTG-102-001: [2672] XMLForm, PAexecute : 29418, Cannot resolve url: ROOT\MYAPP\FRAGMENTOS\MYAPP_FRAGMENTO_DE_CONTROL.xdp.

Do you have any tutorials or guides to help decide a good organization of the forms and fragments in the repository Adobe LC?

Thx

[Former Community Member]

I do not think you will be able to do that .....There is a content root parameter which tells Form Server where your content is located ...normally relative links are used from that location.

Paul

[jpadron_uy]

Ok, so if use forms with fragments necessarily these (XDP and fragments) must be in the repository of LC?

If the XDP (include fragments) is NOT in the LC repository where LC Forms would we look for fragments?

I have not seen any place where these issues are explained in detail.  Where I can get more information about this issue?

Thx.

[Former Community Member]

The fragment location woudl be relative to the location that the form was loaded.

Regarding the docs, if you look at the Forms Server docs it woudl describe the purpose of the Content Root URI parameter not neccesarily all that it can be used for. Note that the same thing woudl apply for any other links (like images) that woudl be on the form.

Here is the writeup that comes from inside of workbench:

The URI or an absolute reference to the location from which form resources are retrieved. When Content Root URI refers to a repository location then it should conform to "repository://authority/resource location". For example if a resource "resourceName" is present and if Content Root URI is set as "repository:/a/b/" then authority is null and resource path is resolved as "/a/b/resourceName", and if Content Root URI is set as repository:///a/b/ then authority is empty and resource path is "/a/b/resourceName", and if resource is "/resourceName" and Content Root URI is set as "repository://a/b" then authority is "a" and resource path is /b/resourceName. Type: string.

Paul