It's not the idea we're objecting to so much as the suggested
implementation.
But the problem is no matter how nice your implementation is, you've
still got to maintain a list of "allowed" classes, which is fine for
you. Unfortunately when you've moved interstate, and your replacement's
replacement adds a class to the package full of "allowed" classes, and
it takes him a week to figure out what the bejesus you did.
-Josh
--
"His comrades fought beside him, Van Owen and the rest...
But of all the thompson gunners- Roland was the best."
Josh McDonald
Analyst Programmer
Information Technology
Ph: 61 7 3006 6460
Email: [EMAIL PROTECTED]
>>> [EMAIL PROTECTED] 17/02/2006 11:41:48 am >>>
What is so objectionable about it? If you think securing a method is a
good idea (I'm not sure I do, but let's assume for the sake of
argument), why is this answer "square"? :) I don't doubt there is a
better answer, but what is it?
Frank
Laurie Harper wrote:
> Frank W. Zammetti wrote:
>> I saw a very similar question asked a few months back in a general
Java
>> forum, and I suggested an answer that I've never had the chance to
>> actually try out... the theory is interesting though...
>>
>> In the method you want to "protect", immediately throw an exception
and
>> catch it. Then, parse the stack trace and see who the caller was.
If
>> it's not a class you want to have access to the method, throw an
>> IllegalAccessException.
>>
>> Again, it's one of those things that sounds good in your head, I
have no
>> idea if it translates to anything workable :)
>
> Ewwww! If you're going to reinvent the wheel, at least don't make it
> square ;-)
>
> L.
>
>
>
---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
***************************************************************************
Messages included in this e-mail and any of its attachments are those
of the author unless specifically stated to represent WorkCover Queensland. The
contents of this message are to be used for the intended purpose only and are
to be kept confidential at all times.
This message may contain privileged information directed only to the intended
addressee/s. Accidental receipt of this information should be deleted promptly
and the sender notified.
This e-mail has been scanned by Sophos for known viruses.
However, no warranty nor liability is implied in this respect.
****************************************************************************
