Assuming this emulator is a standard UEI emulator, go to Window, Preferences,
J2ME, Device Management and double-click its entry in the list. Under the
properties tab, you should see a property named "security.domains" that
enumerates the supported trust levels. Now go back to the Wireless Toolkit
Emulator debug configuration for your project and under the Emulation tab,
enter in the desired Security Domain. That should do it.
Parag Chandra
Senior Software Developer
[EMAIL PROTECTED]
404-439-5821
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of nei young
Sent: Friday, February 15, 2008 3:59 AM
To: eclipseme-users@lists.sourceforge.net
Subject: [Eclipseme-users] EclipseME 1.7.7 vs. S60 3rd emulator
Hi group,
I'm using Eclipse 3.2 together with EclipseME 1.7.7 in order to develop
applications for Symbian S60. After tons of problems I'm now having a
situation, that I can edit, sign, run, debug and deploy applications to my
phone. The latter with a valid developer certificate, because I'm using APIs,
accessible for "trusted" midlets only.
The major problem is: How to make the S60 3rd FP1 emulator know, that my midlet
is signed? Whenever I start a debug session, the emulator prints out
"Installing in untrusted mode".
I cannot make Eclise/EclipseME sign my _debuggee_ too (it works for the
package, not for the debuggee).
Can anybody give me a pointer, how to create a "trusted third party" debuggee?
Kind regards
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Eclipseme-users mailing list
Eclipseme-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
