Dennis,
I can give you some examples later if you like, not near any code at the
moment.
Cheers,
Peter.
Peter Firmstone wrote:
You place a file called permissions.perm inside a top level directory
in the bundle.
OSGI-INF/permissions.perm
The syntax is that used for java policy files.
The format is the same as the encoded format of PermissionInfo for
that permission.
The framework limits the permissions to this set, less permissions may
be granted of course, dependant on the bundle signer.
Cheers,
Peter.
Dennis Reedy wrote:
On Feb 14, 2010, at 524PM, Peter Firmstone wrote:
I guess it could be designed in by noting what permissions are
required in the source code. It is possible that the tool might miss
a permission based on the execution path. That's one thing I like
about OSGi bundles, the author of the bundle specifies the
permissions required to execute the code in the bundle.
I guess I could research this, but its easier to ask :)
Can you give me example(s) of what bundle declared permissions look
like?
Thanks
Dennis
