I tend to put log messages in the offending areas and look in ....webapps/cocoon/WEB-INF/logs make sure that WEB-INF/logkit.conf has all the logging turned to DEBUG. The line number in element processor is a good clue.
I kinda think that perhaps your stylesheets have something in common and one is doing something to snuff out an expected value (but thats just an unqualified guess). Wow, writing your own serializer for HSSF sounds a bit extreme...lots of work. What specifically about the current serializer do you dislike? Granted keeping up with Gnumeric's changes to their fileformat (especially since they are less than meticulous about documenting the changes) is somewhat problematic, it beats having no visual representation/check of your design (or at least that was the rationale). I think once you get the hang of the "elementprocessor" architecture, you'll find this one is quite simple. I also think that if you stick a few log statements you'll find out what the problem is. I'll be on this soon as well. Just realize I have a long backlog of "andy-to-do" so if I'm less than fast...well probably another task just was sooner in the queue. Personally, I'd rather see some collaboration on the Serializer then have multiple ones. If you think there is something inherently wrong with the current one (other than the inevitable bugs to be fixed), I'd like to hear your viewpoints on how to improve it. -Andy Seth Ladd wrote: >On Thu, 2002-04-25 at 08:09, Andrew C. Oliver wrote: > >>I've moved both your emails to a folder named tasks. I will look at >>this and get back to you. By the looks of this error it looks like >>invalid data (a null where it expects characters). >> > >Thanks! > >I'll keep poking around, trying different things. Is there a strategy >for debugging? I'd like to do a trace, or watch what happens to try to >identify the offending data. > >What confuses me is that if I take the XML being produced and manually >run it through the last step (which is the serializer) then it works >great. It's only when it's being run through the pipeline directly does >it fail. So at first I thought it was bad data, too (as the exception >seems to indicate) but the generated XML seems OK. > >Now, of course, the SAX events might be getting screwed up and it might >only work OK when run through the XML serializer. > >If you have some suggestions on how to get more debug or watch the >processes, that would be wonderful. > >I'll also send you all the style sheets, etc if you'd like to try it. > >Thanks very much, >Seth > >ps In the meantime I'll probably write my own HSSFSerializer (a simpler >one). Maybe this will help track down the problem? > > >--------------------------------------------------------------------- >Please check that your question has not already been answered in the >FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> > >To unsubscribe, e-mail: <[EMAIL PROTECTED]> >For additional commands, e-mail: <[EMAIL PROTECTED]> > > --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faqs.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
