Snapshots might be helpful. We're running .NET web services for our rendering without a problem, but I'm not familiar with the code samples.
It should be working as long as you have the ?blob=base64 added to the service's URL. One thing that you may want to check is if there are any exceptions thrown in the LiveCycle server's log. If something is going wrong then you may get an empty response.
More inputs on this issue (By DougB999's teammate VKG7)
The WebService URL used for LiveCycle ES Output is,
as you suggested I tried to append "blob=base64" to the url but it gave following error,
There was an error downloading 'http://localhost:8080/soap/services/OutputService?blob=base64'.
The request failed with HTTP status 404: Not Found.
but the url with "?wsdl" returns the OutputService Description.
We followed the steps described here in the Quick Start Sample Code,
However the current implementation saves the generated PDF file correctly under the location specified in "fileURI" option.
PDFOutputOptionsSpec pdfOptions = new PDFOutputOptionsSpec();
pdfOptions.fileURI = @"C:\GBS\PDFTemplate\Invoice.pdf";
The way I do it is not by adding the ?blob=base64 string to the WSDL url. Instead I create a web reference using the http://localhost:8080/soap/services/OutputService?wsdl address (I called my web reference LCESOutputService). Then in my code I append the blob string to the service's URL:
LCESOutputServicesvc = new LCESOutputService();
svc.Url += "?blob=base64";
That's the way I do it and it works fine.
Thanks for your valuable inputs .. it really helped..
I appended the "blob=base64" to the web reference URL thinking, that parameter will provide a BLOB specific WSDL.
Also got carried away that in the documentation it was mentioned along with the various the LiveCycle Webservice WSDL urls.
Now I am getting the PDF bytes as a return value..but still I have some other issues and need help,
1) Time to time randomly I get this "exception while resolving a new connection to an Adobe Service". Please see the attached file "RandomError.xml"
2) Now I am getting the generated PDF document as bytes from the return value. But when I checked the saved XML file from
"generatePDFOutputResultDoc.binaryData" there is an error logged. Please see the attached file "OutputError.xml".
3) Is there anyway to avoid saving the generated PDF file (pdfOptions.fileURI) which now I am getting as bytes from the return value.
As I am .NET person and having very little knowledge about Java environment these errors block my progress.
All your valuable idea's welcome.
Its hard to tell from the returned log. The first problem looks like there may be an intermitant problem connecting to the LC web service (perhaps a busy network?)
The second problem is really hard to tell from the returned log. Can you check the application server log (jboss, websphere, weblogic). LiveCycle's pretty expressive when something doesn't work and the server side log may give a better clue as to the nature of the problem.
I don't think the second one is an error at all. It looks like a notification that your submission was successful.