This content has been marked as final. Show 7 replies
I have the same problem...
Is this issue resolved? I am having exactly the same problem! Can any experts please enlighten me on this subject?
Thanks in advanced!
Are you both using the cfdocument tag to create a PDF document in a CFC?
I am asking to make sure that we're all doing the same thing to get the same error, or if we're each doing different things (even minor variations) to get the same error.
Can you file a bug in the Flex bug base at http://bugs.adobe.com/flex/ and include a small reproducible test case (MXML and CFCs, if possible) and we can take a look.
Also, if you can post the bug number here so others can vote/subscribe, that would help a lot.
Done. The bug number is: SDK-14762
If you're experiencing this problem, please vote for the issue here:
Thanks for the tip, Peter.
Any luck figuring this one out? I'm wondering if this error has to do with this "Note: ColdFusion MX does not return HTML and CFML outside of the <cfdocument> </cfdocument> pair."
I'm just thinking out loud but I wonder if the rest of the cfc code gets ignored after you close cfdocument. So any message reporting hangs. Just a thought.
FYI - I voted for your bug posting.
Yes, through a suggestion on another forum I came up with a work around. Rather than using the saveAsName attribute in the cfdocument tag in my CFC I switched to using filename. When using the filename attribute the pdf is created and saved into the same directory as the cfc, but now you also have the ability to return the filename to Flex.
I created a function in my Flex app to receive the filename and then used the URLRequest function to pull up the the PDF as an external file.
Does that make sense?