- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Okay, I think I see a potential problem;
The renderXDP operation is part of the Content Services samples and is meant to be used as part of the Content Services module. Its actually a small workflow that reads the XDP from the repository, renders it (using renderPDFForm) and then applies reader extensions.
You say that you are taking the result and doing something with Assembler. I'm not sure what you are doing with Assembler, but manipulating the document after reader extensions have been added can result in some weird errors (although its the first time I've seen the one you mention).
It would be better to do the following:
- Read your content
- Call Forms
- Do your Assembler stuff. Can you tell me what you are using Assembler for? There may be an easier way to do this.
- Add Reader Extensions
You can either do this in a process and make one API call, or call each operation individually using the API.
Views
Replies
Total Likes