Interesting thought; I think what I really want to add is artifact visibility, so that your configuratoin would only be accessible from within your module (for both read and write).
On Sun, 1 Aug 2004 09:53:33 -0700, Naresh Sikha <[EMAIL PROTECTED]> wrote: > I would like to state that my configurations are "read only" so that > they cannot be modified by just anyone who can find it in the > Registry. > > Is this possible? > > My current workaround is to have an object that all my configuration > beans extend from that have a readOnly property and an assertion > method that fails if the readOnly flag is set. Then any property > setter first asserts that it is not readOnly. Finally my service that > exposes these configurations first sets any top level readOnly flags > before returning them. > > Thanks. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Howard M. Lewis Ship Independent J2EE / Open-Source Java Consultant Creator, Jakarta Tapestry Creator, Jakarta HiveMind http://howardlewisship.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
