http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2445 *** shadow/2445 Thu Jul 5 23:30:40 2001 --- shadow/2445.tmp.17681 Fri Jul 6 09:37:22 2001 *************** *** 211,213 **** --- 211,245 ---- ------- Additional Comments From [EMAIL PROTECTED] 2001-07-05 23:30 ------- Yeah. It is about cocoon2. Thanx for taking the assignment. + + + ------- Additional Comments From [EMAIL PROTECTED] 2001-07-06 09:37 ------- + In the thread on xalan-dev titled "Re: something funny with namespaces and + xalan2.2dev (fwd)": + + Scott Boag wrote: + > My suspicion is that whoever is generating SAX events within the body + > statement, i.e. the form, input, etc., is not generating the namespaceURI + > argument for startElement. The SAX2DTM will not try and resolve the + > namespace itself, as per: + + Donald Ball <[EMAIL PROTECTED]> replied: + > (sorry for the lateness of this response) + > + > all of the elements in the form were created using SAX by a custom + > component. the component strictly creates nodes in the default namespace: + > + > handler.startElement("","form","form",attributes); + + This by no means will be resolved to namespaced nodes by the DTM, and does not + match the SAX2 contract. Isn't it easy to pass the namespace? + + mkamp (sorry, I don't know your name), does this seem like the same bug? + + > the other elements on the page were generated using SAX by cocoon's + > FileGenerator, which is ultimately using jaxp (xerces) to parse the file. + + Please double-check that the SAXParserFactory has namespace processing turned + on. I did a search for SAXParserFactory, and found it in JaxpParser, and do + see setNamespaceAware(true) being called. So probably these events are being + generated properly.
