Re: BeanShell working in unsigned JWS env.
Mark Swanson <mark-e2GstmqqWGa5mcYau+xr2AC/[email protected]>
| Newsgroups | gmane.comp.java.beanshell.devel |
|---|---|
| Organization | Web Service Solutions, Inc. |
| Message-ID | <[email protected]> |
On April 30, 2004 6:39 pm, Mark Swanson wrote: > > I'm looking forward to some good arguments to allow BeanShell to continue > to violate protected/private classes/members/attributes :-) OK, I think Shankar and Harish have given good reasons to allow protected/private access. Thanks fellas. So I think the patches need to be smarter. Here's my plan: 0. Keep default access to protected/private 1. setAccessible(true) performs a test to see if the env allows it. If not, warns the user. setAccessible(true) test should be called at bsh init(). 2. The few reflection points I changed will be wrapped with the accessible check. 3. Since no one has commented on my System properties solution I'm going to assume no one has a problem with it. I actually don't even know how many system properties there are and if they are for debugging only perhaps this is moot. 4. It's pretty important (critically actually) that certain public methods _never_ get called in the Interpreter. Does anyone have any suggestions on how I can prevent a few known methods from executing? Cheers. -- VoIP SIP:[email protected] Free calendar client and server - works with Exchange/Outlook/Yahoo! TV-Listing and Weather Schedules http://www.ScheduleWorld.com/ http://www.ScheduleWorld.com/sw/ScheduleWorld.jnlp (JWS) ------------------------------------------------------- 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