Exceptions are handled cleanly prior to Render Response (which is the big improvement from the old PPR tech), but anything during Render Response still isn't handled cleanly. The error's inserted into the XML, which means it's no longer valid XML.
I think we'd need to do some JS hacking with: - Checking if the XML is valid (think we already do) - If not valid, parse the text response instead of the XML response and look for an <error> element, then try re-parsing just that as XML, and handling it as an error - If that fails, fall back to a really generic "You're screwed" alert. -- Adam On 8/22/07, Danny Robinson <[EMAIL PROTECTED]> wrote: > Not certain this is attributed to Adam's very latest PPR changes, but an > exception in my renderer code caused the following to be sent back to the > browser during PPR, and caused two further javascript exceptions. From > memory, I thought exceptions were handled cleanly and an alert popped up. > > <SNIP> > <!--Start: > org.apache.myfaces.trinidad.Panel["_id54"]--><span > id_popupTrigger="incExpTable_0__id54"><a > id="incExpTable_0__id54" name="incExpTable_0__id54" > <?xml version="1.0" ?> > <?Tr-XHR-Response-Type ?> > <error status="500"> > java.lang.String > For more information, please see the server's error log for > an entry beginning with: Server Exception during PPR, #1</error> > > > > -- > Chordiant Software Inc. > www.chordiant.com
