There has been some serious interest of late in Avalon and J2ME,
especially as relates to Embedded Controllers for manufacturing
devices and such. There seems to be a clear need for supporting
those devices. The question of the day is what is a comfortable
J2ME spec that we can work within.
It is clear that cell phones and PDAs really should not be our
focus--even though we *technically* could support them at the
interface level. The constraints of such devices would prove too
limiting for our purposes.
I have heard two possibilities:
PersonalJava and CDC + PersonalProfile. Considering that there
is an emulator available for PersonalJava that works in both
Windows and Solaris, I would prefer that we stick to that. The
details of the differences are listed below (as pertains to what
we might care about):
Package PersonalJava PersonalProfile
----------------- ------------------ ----------------
java.rmi.registry Optional unsupported:
java.rmi.RegistryHandler,
java.rmi.LocateRegistry
java.rmi.server Optional Not included
java.beans JDK 1.1.8 fully supported Many classes/
methods not supported
java.rmi Optional some pieces
are missing
java.rmi.dgc Optional Not included
Otherwise, if we code for JDK 1.1.8 compliance for the rest of
the stuff (i.e. java.io, java.net, java.security, java.util,
etc.) then we would satisfy both PersonalProfile and PersonalJava
(I believe).
I suggest we go for *interface* compliance of JDK 1.1.8/PersonalJava
Implementation compliance is a matter of community support.
Would this plan satisfy the requirements of the J2ME users out there?
If so, would Avalon ME need to be supported by a SourceForge project,
or would it be supported here? I know the *focus* of Avalon should be
J2SE and higher, but as previously mentioned there is demand for an
Avalon ME container.
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
