Hi,

Thank you for your explanations about serialization, i'm glad having learnt a
few things, such as what the "private static final long serialVersionUID =
3487495895819000L;" field is used to.

I've read much documentation about Jade, but i have NEVER seen anything saying i
have to take care about the class hierarchy or JVM version for the mobility,
except for MIDP. More over, my movable agent extends the Agent class, which
contains "private static final long serialVersionUID = 3487495895819000L;",
and extends himself directly the object class. If've well understood what you've
told me about serialization, the class hierarchy is not a problem.

Moreover, i've once made a mistake, and rather than using the 1.4.2 i was using
the 1.6 for a mobility test where i was always staying on the same machine and
jvm (i've checked on both consoles with java -version), and the mobility didn't
work.

About MIDP and pcsl, a friend has made a script i use to compile the VM.
MIDP=true because when i tried with false, the MIDPPkgChecker.class file was not
generated and was declared as missing. The file follows, but i've also changed
the cdc/build/linux-arm-generic makefile to change "CVM_TARGET_TOOLS_PREFIX=" to
"CVM_TARGET_TOOLS_PREFIX?=".

#!/bin/bash # # This script assumes the following dir layout: # 1) the script starts in the directory under whicj there are # following dirs: cdc, jump, midp, pcsl, tools # # 2) these dirs hold the corresponding components, *without* additional # hierachy. E.g. one can use the following commands to checkout # current trunks for all components # # svn checkout https://phoneme.dev.java.net/svn/phoneme/components/cdc/trunk
cdc # svn checkout https://phoneme.dev.java.net/svn/phoneme/components/jump/trunk
jump # svn checkout https://phoneme.dev.java.net/svn/phoneme/components/midp/trunk
midp # svn checkout https://phoneme.dev.java.net/svn/phoneme/components/pcsl/trunk
pcsl # svn checkout
https://phoneme.dev.java.net/svn/phoneme/components/tools/trunk tools # # The settings one might need to tweak are located at the top of the script # # Last updated on mai 2008

# Controls if CDC only (without JUMP) configuration is build (JUMP_BUILD=false)
or CDC + JUMP configuration (JUMP_BUILD=true) JUMP_BUILD=false

# Provide your path to JDK 1.4.2 here export JDK_HOME=/usr/lib/j2sdk1.4.2_16

# define cross toolchain export CVM_TARGET_TOOLS_PREFIX=/usr/local/arm/oe/bin/arm-linux-gnueabi-

# Unit tetsing related settings # Provide your path to JUnit3.8.1 junit.jar (defaults to
/usr/share/ant/lib/junit.jar---standard path for, e.g., Synaptic Manager) export JUNIT_JARFILE=/usr/share/java/junit-3.8.1.1.jar

# Select which graphical porting layer we use export AWT_IMPLEMENTATION=gunit #export AWT_IMPLEMENTATION=qt

# if use Qtopia as graphical porting layer export QT_TARGET_LIB_DIR=/usr/local/qtopiarm/lib export QT_TARGET_INCLUDE_DIR=/usr/local/qtopiarm/include/ export QTEMBEDDED=false export QTOPIA=false

# Enable special mode export CVM_DEBUG=true export USE_AAPCS=true export CVM_ARM_HAS_WMMX=true export CVM_OPTIMIZED=true export CVM_CLASSLOADING=true export CVM_SERIALIZATION=true export CVM_REFLECT=true export CVM_DYNAMIC_LINKING=true export CVM_JIT=true export CVM_JIT_REGISTER_LOCALS=true #export OPT_PKGS=all

## Stanadard settings: modify them at your own risk TOP_DIR=`pwd`

export USE_MIDP=true export CVM_DUAL_STACK=true export USE_SCRIPT_UTILS=true export USE_JUMP=$JUMP_BUILD export J2ME_CLASSLIB=cdc

export JUMP_DIR=$TOP_DIR/jump export MIDP_DIR=$TOP_DIR/midp export PCSL_DIR=$TOP_DIR/pcsl export TOOLS_DIR=$TOP_DIR/tools

# Launch the build cd cdc/build/linux-arm-generic make $@ INSTALL_PATH=/home/colibri/rootfs/usr/local/phoneme sudo cp -R bin $INSTALL_PATH/ sudo cp -R lib $INSTALL_PATH/ sudo cp btclasses.zip $INSTALL_PATH/ sudo cp democlasses.jar $INSTALL_PATH/ sudo cp testclasses.zip $INSTALL_PATH/

...............................EOF

Maybe do you have another target than linux-arm-generic you would recommand to
me ? The VM is intended to run on a toradex colibri PXA270, maybe the
linx-arm-bulverde would be slightly more suitable, but as I'm not used to
cross-compilation and hardware stuff I'm not so sure, and there is also a
buldverde"mv"? I'm not sure it would solve my problem though..

Thx and have a good week-end [Message sent by forum member 'fpillone' (fpillone)]

http://forums.java.net/jive/thread.jspa?messageID=277707