Raymond Auge
> To: Equinox development mailing list
> Date:2013/04/18 12:29
> Subject:Re: [equinox-dev] PermissionInfoCollection issues with
> perms cloning
> Sent by:equinox-dev-boun...@eclipse.org
> --
>
>
&g
Alliance
hargr...@us.ibm.com
office: +1 386 848 1781
mobile: +1 386 848 3788
From: Raymond Auge
To: Equinox development mailing list
Date: 2013/04/18 12:29
Subject: Re: [equinox-dev] PermissionInfoCollection issues with
perms cloning
Sent by:equinox-dev-boun...@eclipse.org
PS: We were not loading our permissions from a standard policy file. Hence
how we ended up with what we have.
On Thu, Apr 18, 2013 at 12:26 PM, Raymond Auge wrote:
> Ok, I stand corrected. After looking at the code for PolicyParser it seems
> the 0, 1, 2 rule is indeed the case.
>
> Other docume
Ok, I stand corrected. After looking at the code for PolicyParser it seems
the 0, 1, 2 rule is indeed the case.
Other documentation seems to have implied that an arbitrary number of
constructor arguments were acceptable:
http://docs.oracle.com/javase/6/docs/technotes/guides/security/crypto/Crypto
> Essentially the PermissionInfoCollection.addPermissions method
> attempts to create a "copy" of the permission for the purpose adding
> to it's collection.
Also, to be clear, there is no copying going on here. The code needs to
construct a Permission object from the information in the Permissi
g list
Date: 2013/04/18 11:23
Subject: Re: [equinox-dev] PermissionInfoCollection issues with
perms cloning
Sent by:equinox-dev-boun...@eclipse.org
Hey guys, thanks for responding.
Forgive me for using the work "clone" (however, it really should be a
clone in my mi
ff Member, IBM
> OSGi Fellow and CTO of the *OSGi Alliance* <http://www.osgi.org/>*
> **hargr...@us.ibm.com*
>
> office: +1 386 848 1781
> mobile: +1 386 848 3788
>
>
>
>
>
> From: Raymond Auge
> To: Equinox development mailing list
> Da
evelopment mailing list
Date: 2013/04/17 18:23
Subject: [equinox-dev] PermissionInfoCollection issues with perms
cloning
Sent by:equinox-dev-boun...@eclipse.org
Hello All,
The current implementation of PermissionInfoCollection uses a rather odd
method of cloning permissions wh
empty map when deserialed.
Tom
From: Raymond Auge
To: Equinox development mailing list ,
Date: 04/17/2013 05:23 PM
Subject:[equinox-dev] PermissionInfoCollection issues with perms
cloning
Sent by:equinox-dev-boun...@eclipse.org
Hello All,
The current
Hello All,
The current implementation of PermissionInfoCollection uses a rather odd
method of cloning permissions which breaks our implementation.
Would anyone object to a new cloning technique which relies purely on
serialization (which is a required interface of permission impls)?
I'll provide
10 matches
Mail list logo
