hivemind-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Carman" <>
Subject RE: Read Only Configurations
Date Mon, 02 Aug 2004 09:11:31 GMT
This one reason why the getConfiguration() method should be taken out of the
Registry interface (IMHO).  

-----Original Message-----
From: Howard Lewis Ship [] 
Sent: Sunday, August 01, 2004 1:33 PM
Subject: Re: Read Only Configurations

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 <>
> 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:
> For additional commands, e-mail:

Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind

To unsubscribe, e-mail:
For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message