RE: BeanShell working in unsigned JWS env.
"Shankar Unni" <[email protected]>
| Newsgroups | gmane.comp.java.beanshell.devel |
|---|---|
| Message-ID | <[email protected]> |
> I believe my changes are correct for any environment > BeanShell is used in. If you think differently, post a single > example where you believe BeanShell should be able to violate > Java's protected and private access controls. Scripted access is used for a lot of things. There's a reason Java makes the internals of classes visible via reflection: various stub- and glue-type packages need to reach into and access and modify private data members. White-box testing involves peeking into the internals of classes and verifying their state. It's not appropriate to enforce "strict java semantics" in this environment. Like I said, if the deployer of the beanshell package wants to enforce strict java semantics, that's up to them. Not to the final user of the scripting package, and also not to the implementors of BeanShell. ------------------------------------------------------- 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