Joseph,
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
>
> >And the SerializerToXML.startPrefixMapping method is still empty so I
> >guess it did not fix the problem.
>
> The fact that the serializer ignores the start/endPrefixMapping calls
> doesn't necessarily mean it "ignores namespaces". All the information
> _should_ be available from the startElement and endElement calls, and the
> serializer ought to be able to do the right thing.
>
OK. I'm not an expert in SAX stuff... I was just refering to that because
the proposed patch was adding code in startPrefixMapping.
>
> > Is it correct to consider 'xmlns:java' an attribute ???
>
> Yes. Note that the prefixMapping feature of SAX is documented (in
> http://xml.apache.org/xalan-j/apidocs/org/xml/sax/ContentHandler.html) as
> something most applications won't need. It's primarily intended to support
> handling of prefixes that appear inside document _content_.
Ok, but then why aren't other namespaces sent as attributes then ?
Anyway I'll check for more evidence, and try to understand the real problem
then.
>
> The serializer isn't doing anything along those lines, so discarding these
> events is perfectly reasonable and the fact that this method is empty is
> probably not a bug.
>
> That doesn't necessarily mean that nothing's wrong. It does mean we should
> take a step back and get a testcase that demonstrates the real problem,
> then use that to determine whether the bug is in the serializer or in the
> data being fed to the serializer.
>
> What's happening that shouldn't be, and how can we reproduce it for
> analysis?
I'll try to put up a basic XML and XSL to reproduce the problem.
More on this later in the day (European time :)).
Michel.
