Jeff Turner wrote:

On Fri, Dec 07, 2001 at 09:17:31AM -0500, Berin Loritsch wrote:

I realized my last post should have had a new title so as not to be lost.
Please come up with issues for Avalon Framework--and we will decide if it
is a showstopper, a minor but allowable change (spelling/correction of
documentation), or something that will be placed on hold.


One issue: DefaultConfigurationSerializer doesn't output xmlns:* elements. Feed it:

<x:foo xmlns:x="http://myco.com/documentation"/>

and you'll get out:

<x:foo/>

I'm not sure how to fix it. Just generate xmlns attributes and hope
javax.xml.transform.sax.TransformerHandler can handle them? Will play
tomorrow..


If it is fixed before I get to it, +1 on commiting the bug fix.




Also, Configuration javadocs need updating to reflect: - the constructor flag system for determining if namespaces are used


+1  (I think I touched on it--but it couldbe made more clear)


- the removal of Namespace


Namespace was never in an official distribution--the only ones who know
about it are people who grabbed an unofficial jar.


 - how getChild("foo:bar") is the non-namespace equivalent of
   getChild("bar").


+1



I'll do that tomorrow.

Btw, namespace support has worked out really nicely.. good work those
involved :)

--Jeff

--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

.





--

"They that give up essential liberty to obtain a little temporary safety
 deserve neither liberty nor safety."
                - Benjamin Franklin


-- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>



Reply via email to