- From: Brian Wilson <bloo@blooberry.com>
- Date: Wed, 29 Aug 2007 23:14:52 -0700 (PDT)
- To: www-validator@w3.org
(I was on vacation for awhile...my apologies for dropping out on this issue for awhile). On Wed, 1 Aug 2007, olivier Thereaux wrote: [comments on helpful fixes for warnings in SOAP trimmed for space] The fixes are exactly what I was hoping for, thanks! > > I'm not sure (without some extensive digging) where the fatal error > > output > > is defined, but perhaps something similar could be done for those > > as well. > > I'm currently doing string matches against the <env:Reason>/<env:Text> > > content when a <env:Fault>/m:exception is encountered, and that > > solution > > doesn't seem very elegant. > > Indeed. Not sure what you mean by "where it is defined" - if you mean > where, in the code, the fatal error output is triggered, the triggers > are scattered through the validator code. But each fatal error has an > id, too, (such as fatal_referer_error, fatal_no_content?) and we > could be using that as well. Would it make your life easier? Yes, I think it would help. Especially if they are scattered around the code, someone intimate with the code would be the best one to make the necessary changes. I'd like to store a very short unique identifier for every error class reported and that would go for fatal errors too. I could intercept those messages and create my own codes, but it would be easier (and maybe for others) if they were already there. -Brian Brian Wilson --------------------------"Those aren't Sex muffins! -Coach bloo@blooberry.com ---------------------Those aren't Love muffins! http://www.blooberry.com ---------------Those are just BLOOberry muffins!" Creator of Index DOT Html/Css: http://www.blooberry.com/indexdot/
Received on Thursday, 30 August 2007 06:14:59 UTC