That has been discussed many times. It is the chief reason why we use Configuration objects and not JDOM.
A component must not _*EVER*_ be able to look at the configuration of another component. There could be sensitive information that is meant for the consumption of only that other component like usernames and passwords. Configuration objects allow you to take any node, and give it to a component--confident in the fact that a trojan component cannot exploit weaknesses in the Configuration object to get unauthorized information. > -----Original Message----- > From: Leandro Rodrigo Saad Cruz [mailto:[EMAIL PROTECTED]] > Sent: Thursday, November 21, 2002 8:37 AM > To: Avalon Developers List > Subject: [CONTRIB] who is my father ? The configuration asks ! > > > Hi all. I'm sending this patches to the list to see if you > would like to > include them into CVS. > > These changes should help a developer, with a Configuration > instance at > hand, determine it's parent and root Configuration instances. > It respects the read-only nature of Configuration objects. > > -- > Leandro Rodrigo Saad Cruz > IT - Inter Business Tecnologia e Servicos (IB) > http://www.ibnetwork.com.br > http://jakarta.apache.org/ojb > > -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
