[ 
http://issues.apache.org/jira/browse/XALANJ-2118?page=comments#action_64819 ]
     
David Bertoni commented on XALANJ-2118:
---------------------------------------

You should read this section of the SAX2 documentation, so you understand what 
the startPrefixMapping() and endPrefixMapping() events are for:

http://www.saxproject.org/namespaces.html

In particular, here is the first sentence in the section "Configuring Namespace 
Support":

"The http://xml.org/sax/features/namespaces feature controls general Namespace 
processing. When this feature is true (the default), any applicable Namespace 
URIs and localNames (for elements in namespaces) must be available through the 
startElement and endElement callbacks in the ContentHandler interface, and 
through the various methods in the Attributes interface, and 
start/endPrefixMapping events must be reported."

Note the last sentence that says "and start/endPrefixMapping events must be 
reported."  There is no legal configuration of a SAX2 XML reader in namespaces 
processing mode that does not deliver these events.  Given that, I don't think 
you can call it a bug if a ContentHandler does not work properly when you don't 
deliver those events.

> No namespace declarations for attributes
> ----------------------------------------
>
>          Key: XALANJ-2118
>          URL: http://issues.apache.org/jira/browse/XALANJ-2118
>      Project: XalanJ2
>         Type: Bug
>   Components: SAX
>     Versions: 2.6
>  Environment: Win XP
>     Reporter: Chris Bitmead
>     Priority: Critical

>
> I'm using Xalan SAX to write OpenOffice.org documents, and these documents 
> sometimes use a namespace "fo" as in "fo:font-family", but it only uses this 
> namespace for attributes, not for tags and Xalan doesn't create the 
> appropriate namespace declaration for these attributes when writing the 
> document out with SAX. I have tried this with the xalan built into Java 1.5.0 
> as well as tried the 2.6.0 xalan.jar dropped into the lib/endorsed directory 
> in Java 1.4.2, but both exhibit this behaviour.
> This seems like a bug to me, is it?

-- 
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]

Reply via email to