Fwiw, I've just submitted code to at least output the message in addition to the code of errors that occur during Shindig rendering requests, which should help significantly when Caja processing errors occur. The rest of these comments still apply though :)
John On Wed, Jan 16, 2008 at 5:44 PM, <[EMAIL PROTECTED]> wrote: > On Jan 16, 2008 2:31 PM, Mike Samuel <[EMAIL PROTECTED]> wrote: > > > Please explain what you mean by (error "code")? > > > > This is all much easier to discuss when we're all looking at the code, but > I'll try. > > The thing in Shindig that does the Cajoling is allowed to throw a > GadgetException. This exception has a code (one of an enumeration, > including > MALFORMED_FOR_SAFE_INLINING) and a message. > > Right now, when Shindig catches one of these exceptions, it returns to the > client only the code, which is why you see <pre>MALFORMED...</pre> and > nothing else. The embedding we have right now formats the Caja > MessageQueue > into the message of this exception, but it's not getting returned to the > client. > > Once we have that licked, the next step will be to format the Caja > MessageQueue messages in a *pretty* way so a developer sees "real compiler > error messages", and work out the file position skew issues caused by the > fact that the container is, in the general case, parsing and, in some > cases, > rewriting the content before it hands it to Caja. > > Ihab > > -- > Ihab A.B. Awad, Palo Alto, CA >
