• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

java.lang.SecurityException: Prohibited package name: java.util.logging

 
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
There is an error when I runs my system outside of the Jbuilder IDE.

The command is like:



The error message is like:



What's wrong?
Does the java needs a security manager to access the java.util.logging package?
 
Hu Yong Jun
Greenhorn
Posts: 26
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I has resolved this problem minutes before.

The src is complied in j2sdk 1.4.2 environment, but I runned it with the old version java.exe.

When I replaces the old java.exe with a 1.4.2 one, it is OK!

The following is found in WWW:




Why does java not allow packages from java.lang when I'm connecting from another machine? I get an unmarshaling error:
java.rmi.UnmarshalException: Error unmarshaling return;
nested exception is:
java.lang.SecurityException: Prohibited package name: java.lang
java.lang.SecurityException: Prohibited package name: java.lang
<exception cut here>
-----------------------------------------------
When mixing different versions of java, the java security manager on the java VM where the catalog is running decides that one version is trying to override the restricted packages. It's not actually true, but that's why it happens. You can prevent this from happening by running the catalog on the lowest version of java that you are mixing together. This usually happens with the iPaq handheld platform (H21). So if you have a machines running jdk1.3.1, 1.4.0 and 1.4.1_beta, the catalog must be run on 1.3.1.



 
Greenhorn
Posts: 4
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
You can not ..... name a package that starts with a Java keyword followed by . operator

i just found the code in Class Loader Class .......that says .....


 
Sheriff
Posts: 11604
178
Hibernate jQuery Eclipse IDE Spring MySQL Database AngularJS Tomcat Server Chrome Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
Hi Hu Yong Jun,

Don't use JDK 1.4 for your assignment, because that would violate this statement from your instructions:

under a production (not development) version of the Sun Microsystems' Java 2 platform and that platform must not have been superseded by a new production version for more than 18 months by the time you make your submission.



Kind regards,
Roel
reply
    Bookmark Topic Watch Topic
  • New Topic