Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-19 Thread Raymond Auge
: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

Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-18 Thread BJ Hargrave
To: Equinox development mailing list equinox-dev@eclipse.org 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

Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-18 Thread BJ Hargrave
list equinox-dev@eclipse.org 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

Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-18 Thread BJ Hargrave
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

Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-18 Thread Raymond Auge
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:

Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-18 Thread Raymond Auge
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 raymond.a...@liferay.comwrote: Ok, I stand corrected. After looking at the code for PolicyParser it seems the 0, 1, 2 rule is indeed the

Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-18 Thread BJ Hargrave
...@us.ibm.com office: +1 386 848 1781 mobile: +1 386 848 3788 From: Raymond Auge raymond.a...@liferay.com To: Equinox development mailing list equinox-dev@eclipse.org Date: 2013/04/18 12:29 Subject:Re: [equinox-dev] PermissionInfoCollection issues with perms cloning Sent

[equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-17 Thread Raymond Auge
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

Re: [equinox-dev] PermissionInfoCollection issues with perms cloning

2013-04-17 Thread Thomas Watson
to an empty map when deserialed. Tom From: Raymond Auge raymond.a...@liferay.com To: Equinox development mailing list equinox-dev@eclipse.org, Date: 04/17/2013 05:23 PM Subject:[equinox-dev] PermissionInfoCollection issues with perms cloning Sent by:equinox-dev