I have added security to the microcontainer/aop-mc-int tests. These tests
can be run as:
Kabir@KabirDell ~/sourcecontrol/microcontainer/aop-mc-int
$ build.sh -f build-test.xml one-test-no-weave-secure
-Dtest=org.jboss.test.microcontainer.test.JMXDecoratedTestCase
Kabir@KabirDell ~/sourcecontrol/microcontainer/aop-mc-int
$ build.sh -f build-test.xml one-test-secure
-Dtest=org.jboss.test.microcontainer.test.JMXDecoratedTestCase
To run the no-weave on in Eclipse one just run the test as a junit test. I'm
fiddling with using a properties file for the TestsPolicyPlugin to set the
correct MBeanPermissions
-----Original Message-----
From: jboss-development-bounces(a)lists.jboss.org
[mailto:jboss-development-bounces@lists.jboss.org] On Behalf
Of Scott M Stark
Sent: 18 October 2006 18:32
To:
JBoss.org development list
Subject: Re: [jboss-dev] Java security in Eclipse
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
>>
>>
_______________________________________________
jboss-development mailing list
jboss-development(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jboss-development