Yeah, this run template looks very similar to the run template I have seen for
other UEI emulators. I've been able to set the default trust level for a
particular emulator by simply plugging in a value for the variable
%securityDomain%. However, I don't know if all emulators support the same trust
levels. The ones listed for the Sun WTK emulators are: manufacturer, minimum,
identified_third_party, unidentified_third_party, maximum. So I guess
manufacturer is "allow access to everything" and at the other end of the scale
is maximum.
If you're not having any luck modifying it this way, you may have to look at
the docs for the emulator/SDK itself. They may provide some custom way of
setting the trust level, either via the emulator itself or via some
configuration file. I was able to adjust the security level for IBM's J9 MIDP
emulator by editing a text file somewhere; hopefully something similar is
possible.
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 1:29 PM
To: [email protected]
Subject: Re: [Eclipseme-users] EclipseME 1.7.7 vs. S60 3rd emulator
This is the basic setup. But this may be changed. So there is a variable
"securityDomain", I can set it to "maximum" or "manufacturer"?
%executable% [%debugPort%|-Xdebug
-Xrunjdwp:transport=dt_socket,suspend=y,server=y,address=%debugPort%]
[%classpath%|-classpath "%classpath%"] -Xdevice:%device%
[%jadfile%|"-Xdescriptor:%jadfile%"] [%verbose%|-Xverbose:%verbose%]
[%heapsize%|-Xheapsize:%heapsize%] [%securityDomain%|-Xdomain:%securityDomain%]
%userSpecifiedArguments% [%target%|%target%] [%otaurl%|-Xjam:transient=%otaurl%]
The SDK contains a uei.properties file in the root:
S60Device.bootclasspath:
C:/S60/devices/S60_3rd_MIDP_SDK_FP1_3/lib/hmidps60v31.jar
S60Device.screen.bitDepth: 12
S60Device.screen.height: 320
S60Device.screen.isColor: true
S60Device.screen.isTouch: false
S60Device.screen.width: 240
S60Emulator.bootclasspath:
C:/S60/devices/S60_3rd_MIDP_SDK_FP1_3/lib/hmidps60v31.jar
S60Emulator.screen.bitDepth: 12
S60Emulator.screen.height: 320
S60Emulator.screen.isColor: true
S60Emulator.screen.isTouch: false
S60Emulator.screen.width: 240
S60Emulator.security.domains: thirdparty
api.class.path: C:/S60/devices/S60_3rd_MIDP_SDK_FP1_3/lib/hmidps60v31.jar
device.list: S60Emulator, S60Device
kvem.class.path:
C:/S60/devices/S60_3rd_MIDP_SDK_FP1_3/bin/epoc32/tools/ecmt/nei.jar
kvem.main: com.nokia.j2me.sei.NokiaEmulator
sdk.home: C:/S60/devices/S60_3rd_MIDP_SDK_FP1_3
As you can see, I already patched this with less success (the security.domains
entry)
Regards
----- Original Message
----- Original Message -----
From: Parag Chandra <mailto:[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, February 15, 2008 7:11 PM
Subject: Re: [Eclipseme-users] EclipseME 1.7.7 vs. S60 3rd emulator
Interesting. I've never worked with that particular emulator. On the
"Basic" tab of that same dialog, under Launch Command Template, do you see
anything like %securityDomain or -Xdomain in there? If so, maybe you can just
plug in a value like 'manufacturer' or 'maximum'.
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 12:53 PM
To: [email protected]
Subject: Re: [Eclipseme-users] EclipseME 1.7.7 vs. S60 3rd emulator
Hi Parag,
thanks for your quick answer. I'm using S60 3rd FP 1. Your idea sounds
promissing, nevertheless under the properties tab there is only entries for
bootclasspath
screen.bidepth
screen.height
screen.iscolor
screen.istouch
screen.width
and none of the entries is editable. Also - in the Wireless Toolkit
Emulator debug configuration this selection box is empty.
This is a snip off of the SDK releas note:
========================================================================
RELEASE NOTE FOR S60 3RD EDITION SDK FOR SYMBIAN OS, 13.02.2007
SUPPORTING FEATURE PACK 1, FOR MIDP
========================================================================
Regards
----- Original Message -----
From: Parag Chandra <mailto:[EMAIL PROTECTED]>
To: [email protected]
Sent: Friday, February 15, 2008 6:31 PM
Subject: Re: [Eclipseme-users] EclipseME 1.7.7 vs. S60 3rd
emulator
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: [email protected]
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
________________________________
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
-------------------------------------------------------------------------
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
[email protected]
https://lists.sourceforge.net/lists/listinfo/eclipseme-users
