-
1. Re: Net.SOAP.wireDump doesn't (seem to) work
DHeadrick Sep 18, 2011 6:50 PM (in response to DHeadrick)Hi, it's me again,
Made some progress. Somewhat desperately, I looked around Acrobat for anything helpful. Under Edit > Preferences > JavaScript, I noticed that the checkbox "Show console on errors and messages" wasn't checked. It didn't take too much Googling to figure out it should be checked (although I've aways received JavaScript-reported errors, like unitialized variables, without this box being checked in the past, so I'm not sure what additional information checking this box will provide).
In any case, once I checked it, the debugger displayed this partially-shown information (comments added by me):
About to attempt SOAP connection <-----this is from my console.println that precedes the Net.SOAP.Connect
Cannot continue printing to the console.Cannot continue printing to the console.
Cannot continue printing to the console.
Cannot continue printing to the console.
About to print services <----this is from my console.println that follows the Net.SOAP.Connect
I'm sure the four "Cannot continue..." messages occurred during Acrobat's attempt to perform the SOAP wireDump. It somehow concluded that it cannot perform the printing, e.g. not enough memory? There is preciously little information on the Internet about this particular message, but at least I have *something* that visibly indicates when Acrobat detects a problem. That's *much* better than the silent failures I had before.
If/when I figure out how to make Acrobat happy and avoid this message, I'll post a follow-up.
If, in the meantime, anyone has any experience with this particular message, I'm all ears.
Thanks.
Dave
