- Mark as New
- Follow
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report
Rohan, thanks for the reply.
Yes, I suppose I could write the file to a temp location then send an html redirect to that location. The temp file would have no security in front of it though. The documents contain personally identifiable information so I can't do that.
I know how to do this if I wrote it myself. We use LiveCycle products to reduce development time. I think that just makes it all the more frustrating that I cannot get Adobe to edit a config file. I started down the road to just write it directly then realized it will cause my users to have a double log in. Then I started researching the use of SSO with Workspace to prevent the double log in. It all just frustrates me even more. My entire app is done and scheduled for production, but failed testing on documents with these MIME types.
If I go down the route of my own servlet to server these documents up, get SSO working, etc. I will end up not using any LiveCycle products in the mix. In the end, at least one product will be dropped from our support renewals. The documents reside in IBM FileNet. I am using the Adobe Connector to IBM FileNet to retrieve them. I would just use the FileNet APIs to pull the document. FileNet returns to correct MIME Type without issue. It only breaks when wrappered with LiveCycle.
Views
Replies
Total Likes