If you see inconsistent behavior its due to different
classpaths/codesources not matching the security policy. I'm ignoring
the obvious solution of not running with a security manager.
What is an example test where you see this?
Kabir Khan wrote:
By "crash" I mean throw a SecurityException
> -----Original Message-----
> From: jboss-development-bounces(a)lists.jboss.org
> [mailto:jboss-development-bounces@lists.jboss.org] On Behalf
> Of Kabir Khan
> Sent: 18 October 2006 16:47
> To: 'JBoss.org development list'
> Subject: [jboss-dev] Java security in Eclipse
>
> When running tests in Eclipse with a security manager enabled
> it allows access to methods that crash when running them from
> the command-line. Does anybody know how to turn off this behaviour?
>
> Thanks,
>
> Kabir
>
> _______________________________________________
> jboss-development mailing list
> jboss-development(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/jboss-development
>
>