Re: Forbidden "internal" packages
On 2009-03-14 22:35:49 -0400, "Qu0ll" <Qu0llSixFour@gmail.com> said:
"Qu0ll" <Qu0llSixFour@gmail.com> wrote in message
news:49bc656e$0$5614$5a62ac22@per-qv1-newsreader-01.iinet.net.au...
[...]
I see. So what is Sun trying to say with this requirement, that this
package shouldn't be used? And why does NetBeans flag it as a
forbidden package?
In fact I am really starting to get the impression that this package is
not to be used. When I run my applet which makes use of those classes
I get this:
java.security.AccessControlException: access denied
(java.lang.RuntimePermission
accessClassInPackage.sun.org.mozilla.javascript.internal)
Is there a way around this without signing the applet?
The sun. package hierarchy is documented[0] on Sun's website as being
part of the implementation of the Sun Java Virtual Machine. Classes and
packages whose names begin with sun. are not guaranteed to exist from
VM release to VM release, to exist from host platform to host platform,
to exist on any other VM, or to be available separately. This applies
to the sun.misc.Base64Encoder class, which comes up in a lot of
poorly-researched examples, too.
You, as an application developer, should probably be talking to the
org.mozilla.javascript. package hierarchy, which is available from the
Rhino download site, or talking strictly to the Java Scripting API (not
to any particular implementation), which will get you the
language-agnostic features but not the Javascript-specific ones. Which
is appropriate is somewhat dependent on your app.
-o
[0] <http://java.sun.com/products/jdk/faq/faq-sun-packages.html>