On 24/09/2012, at 10:21 AM, Tim Worman <[email protected]> wrote: > On Sep 21, 2012, at 5:50 PM, Q <[email protected]> wrote: > >> >> On 22/09/2012, at 6:26 AM, Tim Worman <[email protected]> wrote: >> >>> All: >>> >>> My app is attempting to attach a PDF to an email and I'm getting a failure. >>> The only response is: >>> >>> "Your request produced an error." >>> >>> The code below works fine in development but fails in deployment. I'm using >>> ERJavaMail for sending. >>> >>> There is no stack trace, etc. My attempt to produce my PDF seems to stop at >>> the constructor for FlyingSaucerImpl since no console messages I've placed >>> in the code are seen after that. >>> >>> public void sendEmail() { >>> GSEISPersonAccountInfoComponent acctPdf = >>> (GSEISPersonAccountInfoComponent)pageWithName(GSEISPersonAccountInfoComponent.class.getName()); >>> acctPdf.setAPerson(aPerson()); //create PDFWrapper component >>> NSLog.out.appendln("making pdf"); >>> NSData pdf = acctPdf.generateResponse().content(); //get the PDF data >>> ERMailDeliveryHTML mail = new ERMailDeliveryHTML(); >> >> ^^^^^^^^^^^^^^^^^^ >> >> Does it get this far? >> >> If not, try wrapping it in a try { .. } catch (Throwable e) { log.error(e); >> throw e; } block and log out the error. You may be swallowing the exception >> somewhere higher up the stack, or it's logging out to somewhere you aren't >> seeing in deployment. > > Very mysterious - but I can't get any errors to throw at all. I tried the > approach above. I'm gonna try some other things today and hopefully make some > progress. It's killing me though that I can't get any failure/exception > messages. If it were logging out somewhere else, I'm not sure where that > would be. >
Are you catching Throwable or Exception, and did you wrap everything in the try block? The only reason for you to see your first log message but not your second is because an exception is being thrown somewhere between the two. If you catch Throwable you will intercept it, if you catch Exception you won't. If I were to take a wild guess at the cause of your problem the most likely explanation would be invalid XML data being generated by your component page, possibly an unescaped &, < or > character in some data you are using in production but not in development. _______________________________________________ Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/webobjects-dev/archive%40mail-archive.com This email sent to [email protected]
