we just started a new development project on Java.
We are now at the point that we have installed j9 on the IPAQ but the jxe
file is not executable.
How to start those java programms?
Thanks for your help
Juergen
I don't know on IPAQ but I have a Cassiopeia and to run a jxe prog I had to
do the following :
0- Copy the classes.zip in \My Documents\j9 (for instance)
1- install PalmTweak (I know, it's not only for Palm) :
http://tillanosoft.com/ce/ptweak.html
2- Use PalmTweak to associate jxe files with j9.exe : in application
edit, enter : "\My Documents\j9\j9.exe" "-bm:\My Documents\j9\classes.zip"
"-jxe:%1"
3- you can change the name, the icon, ...
4- Now you can click on a jxe file
chotana
"Jürgen Jung" <jj...@uni-koblenz.de> a écrit dans le message news:
9j6kfv$t0u$1...@news.boulder.ibm.com...
Hope to here soon about possible solutions.
Jürgen
"Jürgen Jung" <jj...@uni-koblenz.de> schrieb im Newsbeitrag
news:9j6kfv$t0u$1...@news.boulder.ibm.com...
--
----------------------------------------------------
Patrick...@oti.com
----------------------------------------------------
"Chotana" <chota...@arsoe-caen.com> wrote in message
news:9j6lge$kci$1...@news.boulder.ibm.com...
>We are now at the point that we have installed j9 on the IPAQ but the jxe
>file is not executable. How to start those java programms?
My first problem with the IPAQ was that i didn't find a command prompt
to enter the j9 commands. A posting of Andrew Sandstrom (copied below)
in this group helped me out.
Lex Sewuster
------------------------------------------------------------------------------------
Instructions for downloading and running the WinCE 2.11 StrongARM
target and demonstrations on an iPaq.
Note that this VM for WinCE 2.11 has not been thoroughly tested on
Pocket PC, but several jxes seem to work.
Download the Windows CE/StrongArm beta from www.embedded.oti.com
(demonstrations and/or runtimes), and install.
This is the HP Jornada 820 demo/runtime download.
Unzip one of the zip files with either a runtime or a net/nonet demo.
For example, j9-arm-wince-1.3-beta.zip.
In any of the zip files, the files necessary for running the j9 VM are
the files that are in the same directory as j9.exe itself (for
example, j9vm13.dll, ivegfx13.dll, etc). The other directories are
used to rebuild the VM and are not needed on the target.
Create a directory, for example "vame1.3", and place j9.exe and all
files in the same directory into it. Locate some of the sample .jxe
files (such as Checkers.jxe, and place them in the vame1.3 directory
as well. This directory should now be transferred to the iPaq using
ActiveSync.
Place iPaq in cradle.
In Windows Explorer, find the "My Pocket PC" icon, which is under
"Mobile Device".
The demo/runtime documentation mentions using the Start/Run menu to
open j9. On Pocket PC there are a few problems:
- The Run menu is hard to find (Press and hold the big button
on the iPaq, then tap on the clock. You'll get a Run prompt).
- the j9.exe and .jxe arguments seem to require a full
pathname. This makes typing in the Run prompt tedious.
You can create a shortcut to j9.exe on Pocket PC. It is just a little
bit of work. For example, assuming you have placed Checkers.jxe in the
vame1.3 directory, do the following to make a shortcut to run j9 with
the checkers demo:
In Windows Explorer on the desktop, find the "My Pocket PC" icon,
which is under "Mobile Device".
Expand this and find the j9 installation (e.g. \vame1.3).
Still in Windows Explorer, right click on j9.exe, and select "Create
Shortcut". Rename this shortcut as desired (eg RunCheckers).
This creates a shortcut to j9.exe, but without arguments.
Unfortunately it looks like you can't set arguments using the
Properties dialog. But you can edit this directly.
Copy this shortcut to a folder on Windows (eg c:\temp\). You don't
seem to get editing capability when under My Pocket PC\Mobile
Device\vame1.3.
Edit this file (RunCheckers.lnk) with an editor (e.g. Notepad).
This file looks like:
17#"\vame1.3\j9.exe"
17 is the number of characters after the #. You can add arguments
after the j9.exe, by adding extra quoted tokens. Adjust the number at
the front of the file accordingly. Note that the first quoted token
should be the full path to the executable and nothing else.
For example:
46#"\vame1.3\j9.exe" "-jxe:\vame1.3\Checkers.jxe"
Save this file, and copy back to "My Pocket PC" in the \vame1.3
directory.
From the device, tap on this shortcut. You should be running the
checkers demo.
--------------------------------------------------------------------
In fact I don't use -bm ;o) but I have to use -bp or -bpa otherwise i won't
work.
chotana
"Patrick Mueller" <patrick...@oti.com> a écrit dans le message news:
9j72v2$bb4$1...@news.boulder.ibm.com...
--
----------------------------------------------------
Patrick...@oti.com
----------------------------------------------------
"Chotana" <chota...@arsoe-caen.com> wrote in message
news:9jjf8h$21ne$1...@news.boulder.ibm.com...
Thanks.
Marc
-------------------------------------------------
Marc Schier
Systems Engineer
Infogation Corp.
San Diego, CA
"Patrick Mueller" <patrick...@oti.com> wrote in message
news:9jjtau$sr0$1...@news.boulder.ibm.com...
You need to do all of this so that the SmartLinker GUI bits include the
appropriate lines in the .opt file. Basically, you should see the following
line (or similiar) in your .opt file:
"@{{IVEHOME}}{{/}}lib{{/}}jclXtr.jxeLinkOptions"
If the JCL just gets included in your opt file via something like:
- cp {{IVEHOME}}/lib/jclXtr/classes.zip
you will be missing important stuff that allows the JCL classes to be
included correctly in the jxe.
I don't know about the size difference, but in general a reduced jxe
(removeUnused option on) with arbitrary JCL and ive.jar and application
classes will be smaller than the classes.zip + ive.jar + application
classes. The downside is that if you have MULTIPLE jxes this way, you will
have the JCL included multiple times in each jxe. If you look at the
jxeRunner example, you can see how it would be possible to build one 'base'
jxe with a launcher that could be used by all your applications, but this
will require you to have some frameworky stuff in your app.
--
----------------------------------------------------
Patrick...@oti.com
----------------------------------------------------
"Marc Schier" <msc...@pacbell.net> wrote in message
news:9jqaaf$s2m$1...@news.boulder.ibm.com...