Updated J2ME (with MicroEmu) setup guide
Sam Halliday
I recently updated my guide to getting started with a cross-platform
J2ME setup
http://javablog.co.uk/2008/01/17/j2me-development-on-os-x-revisited/
I've now given up with EclipseME and moved on to Ant with Antenna.
Actually I've also moved to NetBeans. And Bluecove is now stable on OS
X... thanks Vlad!
When I was setting up my system, I realised that one still needs the
SUN WTK/PhoneME jar files to get a working setup, despite the new
stubs from MicroEmu... and it's all due to naming conventions. It
seems that Antenna and NetBeans know the naming conventions for all
the JSRs that come with the SUN WTK. It would be good if MicroEmu
replicated this convention so that the tools can be tricked into
thinking that MicroEmu *is* the SUN WTK.
Doing an ls gives me
cldcapi10.jar jsr184.jar jsr75.jar satsa-jcrmi.jar
cldcapi11.jar jsr211.jar midpapi10.jar satsa-pki.jar
j2me-ws.jar jsr226.jar midpapi20.jar wma11.jar
j2me-xmlrpc.jar jsr229.jar midpapi21.jar wma20.jar
jsr082.jar jsr234.jar mmapi.jar
jsr179.jar jsr238.jar satsa-apdu.jar
jsr180.jar jsr239.jar satsa-crypto.jar
Additionally... it would be incredibly useful if MicroEmu came with a
"bin/emulator" script that launches MicroEmu. This is because the J2ME
tools (including NetBeans) expect to find such an executable in there,
which should be launchable like so
"{platformhome}{/}bin{/}emulator" {device|-Xdevice:"{device}"}
{jadfile|-Xdescriptor:"{jadfile}"} {securitydomain|-Xdomain:
{securitydomain}} {cmdoptions}
or in debugging mode with
"{platformhome}{/}bin{/}emulator" {device|-Xdevice:"{device}"}
{jadfile|-Xdescriptor:"{jadfile}"} {securitydomain|-Xdomain:
{securitydomain}} {debug|-Xdebug -
Xrunjdwp:transport={debugtransport},server={debugserver},suspend={debugsuspend},address={debugaddress}}
{cmdoptions}
where NetBeans fills in the parameters in curly braces.
Would it be possible to write such a wrapper script? If not... what is
the command to start MicroEmu in debugging mode? I've never had to
start something in debugging mode before, the IDE usually takes care
of it for me.
With these 2 changes... it would mean that the only critical thing
MicroEmu is missing (from being a WTK) would be the preverify command.
I understand that ProGuard is still too buggy to be used as a
preverifier, so I'm sticking with the binary that comes with PhoneME.
Bartek Teodorczyk
On Jan 19, 2008 1:07 PM, Sam Halliday <Sam.Ha...@gmail.com> wrote:
>
> Hi all,
>
> I recently updated my guide to getting started with a cross-platform
> J2ME setup
>
> http://javablog.co.uk/2008/01/17/j2me-development-on-os-x-revisited/
>
Nice to read really interesting article.
> I've now given up with EclipseME and moved on to Ant with Antenna.
> Actually I've also moved to NetBeans. And Bluecove is now stable on OS
> X... thanks Vlad!
>
Integration with IDE's is the thing that we are very aware of, rather
we would like to be. But as always we lack of manpower and a lot of
features are always postponed.
Currently we are preparing to the 2.0.2 release and I'm sure that we
don't include any new feature for it, it's too dangerous at this
point.
Right after that we start planning for new things that we want to
include in new release, believe me there are a lot items to do. I'm
sure that we go back to your request then.
Command to run MicroEmulator in debug mode is the same like to run any
other Java program in debug mode, e.g.:
java -jar microemulator.jar
-agentlib:jdwp=transport=dt_socket,address=8000,server=y,suspend=n
Bartek
BTW Proguard 4.1 has improved preverification code, have you tried it?