One second, I know where the bug is ..... I will fix it in the nightly build.
Tinny
Tinny Ng wrote:
> David,
>
> > SAXParser in the 1.5 release now defaults to doing namespace processing.
> No, I didn't make this. The default namespace setting for SAXParser still
> "supposed" to be off, unless there is a bug. In XMLScanner constructor, the
> fDoNamespace is false. And it is set to true if setDoNamespace(true) is called
> or if the validator requires namespace:
>
> // So lets ask the validator whether it requires namespaces or not. If it
> // does, we have to override the namespace enablement flag.
> if (theValidator->requiresNamespaces() && !fDoNamespaces)
> setDoNamespaces(true);
>
> If you have a test case that shows the problem, please send it to me and I will
> investigate. Thanks!
>
> Tinny
>
> [EMAIL PROTECTED] wrote:
>
> > SAXParser in the 1.5 release now defaults to doing namespace processing. I
> > think it must be related to some change in the default behavior of
> > XMLScanner, but I haven't had a chance to investigate.
> >
> > This seems wrong as there is no way to get namespace information through
> > the SAX1 DocumentHandler. Is this a bug, or was it intentional?
> >
> > This has broken Xalan-C, so I'll need to add a fix to Xalan if this
> > behavior is intentional.
> >
> > Dave
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
