On Friday 06 February 2004 03:22, Leo Simons wrote: > uhm...yes. I'm a bit hazy on the details of package security. Isn't jar > signing something that was added at some point much later than the > original security stuff? I seem to recall it didn't work often, hence > was not safe to assume. Hmm.
You need some ReflectionPermission to 'hack' the private methods, but most people seems to assign AllPermissions anyway... :o( > > Just to remind you, the "modifier hierarchy" is; > > public -> protected -> package -> private > > but I can't s/ package / private / as 'package' is not a keyword! ;) Talk about the lazy programmer. Can't Eclipse and other Refactoring tools manage this? Select all package protected methods, right click, change modifier. What a bummer by Sun to exclude the "package" as a modifier... End of the day, I never rely on 'vigilante users' of my code, they can always screw around with it, I just want protection against myself and well-meaning colleagues, and in that package protection does a pretty good job. Niclas --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
