This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 61891 - JAR execution problem
Summary: JAR execution problem
Status: CLOSED WONTFIX
Alias: None
Product: javame
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 4.x
Hardware: Other Windows XP
: P3 blocker (vote)
Assignee: Martin Ryzl
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-06 17:36 UTC by tark
Modified: 2006-10-23 16:41 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description tark 2005-08-06 17:36:06 UTC
[cut]
run:
Starting emulator in execution mode
Running with storage root DefaultColorPhone
Incorrect domain name, switching to 'untrusted'
java.lang.SecurityException: untrusted domain is not configured
        at com.sun.midp.security.Permissions.forDomain(+98)
        at com.sun.midp.dev.DevMIDletSuiteImpl.create(+39)
        at com.sun.midp.dev.DevMIDletSuiteImpl.create(+62)
        at com.sun.midp.main.Main.runLocalClass(+20)
        at com.sun.midp.main.Main.main(+116)
Execution completed.
16457 bytecodes executed
0 thread switches
738 classes in the system (including system classes)
229 dynamic objects allocated (15504 bytes)
1 garbage collections (0 bytes collected)
BUILD SUCCESSFUL (total time: 4 seconds)



It's error occures when I try to run MIDP application(jar). My program perfectly runs 
on KToolbar J2WTK 2.2. But NetBeans.. Compile & build is without errors. All 
options by default (choose domain to "trusted", "untrusted" and other were not 
help).

NO ONE midlet from WTK samples, which I try to execute after build, do not 
runs... Is it possible Java security feature? 
What can I do??? 

With best regards, Tark ( z-tark@rambler.ru )

P.S. Sorry for bad engish =(
Comment 1 Adam Sotona 2005-09-02 10:36:30 UTC
I've seen this problem and already reported to J2ME Wireless Toolkit.
It usualy happens when some non-ascii characters are present in its installation
path or even in a path of the executed application.
I think that running netbeans with argument -userdir
<some_directory_without_native_characters> and moving all your projects to a
location where the path will not contain the native characters will help you.

I understand this is very annoying an I hope it will be fixed by J2ME Wireless
Toolkit Team soon.
Comment 2 Lukas Hasik 2006-01-17 13:57:31 UTC
verifying all old issues