[
http://issues.apache.org/jira/browse/XALANJ-2111?page=comments#action_63669 ]
Brian Minchau commented on XALANJ-2111:
---------------------------------------
Just in case these lines slide around, the lines refered to by Antonio are
these in the SAX startElement() method:
// if this element has a namespace then treat it like XML
if (null != namespaceURI && namespaceURI.length() > 0)
{
super.startElement(namespaceURI, localName, name, atts);
return;
}
and these in the endElement() method:
// if the element has a namespace, treat it like XML, not HTML
if (null != namespaceURI && namespaceURI.length() > 0)
{
super.endElement(namespaceURI, localName, name);
return;
}
I agree with Henry, we need to follow 16.2 of XSLT 1.0, so we can't just cut
them out. We need a testcase to investigate the NPE.
> NPE in o.a.xml.serializer.ToHTMLStream.endElement()
> ---------------------------------------------------
>
> Key: XALANJ-2111
> URL: http://issues.apache.org/jira/browse/XALANJ-2111
> Project: XalanJ2
> Type: Bug
> Components: Serialization
> Versions: 2.6
> Environment: Cocoon 2.1.7
> Reporter: Antonio Gallardo
>
> See: http://issues.apache.org/bugzilla/show_bug.cgi?id=34386
> The solution is to comment lines blocks from 726 to 731 and 840 to 845 in
> org.apache.xml.serializer.ToHTMLStream.java (current CVS).
> This makes the serializer to service the SAX events as XML and this seems to
> be
> the cause of the trouble.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]