Re: BeanShell working in unsigned JWS env.

Mark Swanson wrote:

>Hmm, further searching the commands revealed setAccessibility. I'm guessing 
>that's what you meant. If yes, I would like to put to the list that 
>setAccessibility() should be removed because:
>1. I think it is wrong in any case to violate something so (sacred?) as 
>protected/private.
>2. In my experience it is never a good idea to bypass the public interface. 
>Can anyone give a single good reason why they think this is a good idea?
>
>  
>
I am using the package protected classes from the Beanshell API to 
access its AST. So if this is to happen I would like to have access to 
the ASTs in another form. In any case I think a scripting language 
should be more forgiving and liberal than a strictly typed language and 
when such access is possible even in a strict language like Java, it 
makes no sense to me to make such restrictions in Beanshell.

-Harish



-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g. 
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click