Berin Loritsch wrote:
>
> Sylvain Wallez wrote:
> >
> > Hi all,
> >
> > I've tried to use the new namespace-aware Configurations and encountered
> > serious problems : each Configuration is given the latest namespaces
> > declared whatever its actual namespace is.
> >
> > For example :
> > <?xml version='1.0'?>
> > <ns2:config xmlns:ns1='namespace-1' xmlns:ns2='namespace-2'>
> > <ns1:child name='child-config'>
> > <foo>value of blah</foo>
> > </ns1:child>
> > </ns2:config>
> > leads to all elements being marked as belonging to "ns2" (the latest one
> > declared).
> >
> > So please find attached a patch for both SAXConfigurationHandler and
> > DefaultConfigurationSerializer.
I applied your patch, with the modification that the Configuration object's
getName() returns the local name (what was always considered correct).
Please crosscheck.
--
"Those who would trade liberty for
temporary security deserve neither"
- Benjamin Franklin
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
