Leo Sutic wrote:
In short, this would allow us to move the setting of fields to the container. The container can access private fields via the AccessibleObject.setAccessible, provided that the container class has the required security permissions (which I assume it can be given - it is the only class that needs it).
Thoughts?
Maybe I'm just too old fashion - but this is like sleeping with the enemy. If I - as component writer declare something as private - then what I'm saying is that its off limits to others including the container.
Stephen.
--
Stephen J. McConnell mailto:[EMAIL PROTECTED]
|------------------------------------------------| | Magic by Merlin | | Production by Avalon | | | | http://avalon.apache.org/merlin | | http://dpml.net/ | |------------------------------------------------|
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
