Re: Test - trust in JNLP exntensions
On Oct 1, 2:24 pm, Roedy Green <see_webs...@mindprod.com.invalid>
What is the disadvantage of requesting all permissions for everything
and signing with the same cert?
In theory, none. (All Jars are actually signed
with the same certificate).
The thing is, I might want to use one of the Jars in
two apps. One that requires all-permissions, and
another that only requires j2ee-application-client-permissions
(JACP) or can be sandboxed.
Further, a free floating element such as a dialog
might be supplied with either no or JACP permissions.
Since I was also playing with lazy downloads, I
decided it might be easier to have each package in
it's own extension, declaring the permissions
and download strategy...
...actually I am having a hard time justifying my
decision to have every package referred to in its
own JNLP(s), since most of that stuff I was talking
about can be done in the main JNLP, and the rest
is of little relevance.
Stuff it. I have now directly imported all Jars
into the main JNLP, and it works as expected.
I may revisit this topic later (with a possible
view to raising a bug report), but for the moment
I just want it working.
DukeBox still needs some further honing, and
much more testing, but I'll leave that for
Thanks all, for your attention and help.