Thank you Andrew . Will surely consider your suggestion.

One more thing is bug in present code is found

I had kept empty string for local name of attribute

atts.addAttribute("", "", attName, "CDATA", attValue);

this was creating conflict when i was using

xmlHandler.startElement(XMLConstants.NULL_NS_URI, nodeName,nodeName, atts);

So finally the solution is local name of attributes and startelement should have a value.

cheers :)  


From:        Andrew Welch <>
To:        Mailing list for the SAXON XSLT and XQuery processor <>
Date:        10/13/2011 04:29 PM
Subject:        Re: [saxon] Parser configuration problem: namespace reporting is        not enabled

On 13 October 2011 11:48,  <> wrote:
> Hi Andrew,
> Ya i had a look into the code you posted.
> ---> Ultimately though, the code is a mess, even once you fix that you will
>     just run into another problem... maybe consider using XOM or JDOM
>     instead.
> Can you tell me what kind of another problem i may run into ?

Yep - generating the events in the right order.

Andrew Welch

All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
saxon-help mailing list archived at