14
resources/META-INF/MANIFEST.MF
within its root folder. The adderlib
extension
has such
a
file, whose content is
FavouriteSnake: Viper
This defines a property whose value will be available to all applications in a similar fashion to
application-specific manifest properties. The
addertest
application demonstrates this by displaying
the value of this property. The library suite is built to contain all the properties defined by the
manifests of all its input jars. For more details on accessing these properties, see the section
Manifest and resources.
• Running startup code
• Some library extensions require initialisation to be performed at startup (for example, to
create daemon threads). To specify startup code that must be run, add one or more lines to
the manifest properties of the library extension with the following format:
spot-startup-xxxx: my.fully.qualified.Classname
where
xxxx
is a string that is provided as the single argument to the static
main()
method of
Classname.
Startup code is run only in the master isolate. It is run after all normal spotlib initialisation is
completed but before the OTACommandServer (if configured) is started and before the application
is launched.
• Modifying the system library code) for properties that are constant for all your Sun SPOTs
and applications.
Built-in properties
There are a number of properties with reserved names that the libraries understand. These are:
DefaultChannelNumber
DefaultPanId
DefaultTransmitPower
com.sun.spot.io.j2me.socket.SocketConnection-BaseStationAddress
com.sun.spot.io.j2me.socket.SocketConnection-BaseStationPort
The first three control the radio’s operation; see section Using manifest properties to adjust the
radio. The last two control the socket connection that underpins http access: see the section
Configuring the http protocol.
Using the Basestation
Overview
The purpose of the Sun SPOT Basestation software is to allow applications running on the Host to
interact with applications running on Targets. The physical arrangement is: