Node start-up
Node is the starting point of the platform. It is responsible for creating component registry and createing a starter instance based on the class read from command line arguments (see node command line arguments section for detailed list of available commands). Than the processing is passed to the starter instance and, since this moment, the starter instance manages platform life-cycle.
See more details about default starter at batch mode single starter page .
The detailed sequence of node start-up is presented at the following diagram:
Command line arguments
Default (platform) command line arguments:
- -starter - (required) the fully qualified name of starter class
e.g:-starter org.jage.platform.starter.batch.single.BatchModeSingleStarter - -help - prints usage message
- -Dproperty=value - properties defined by various modules
Each module can define custom options which have -Dage prefix (eg. -Dage.node.conf=classpath:age.xml). See modules' documentation for more details.
Resource specification
When specifing a resource to load by the platform (e.g. a configuration file in the age.node.conf option) it is possible to use different protocols.
Following protocols are available and recognised by default:
- classpath — for loading files from paths in the current classpath, e.g.:
classpath:org/example/age.xml
- file — for absolute or relative paths in the filesystem, e.g.:
file:/home/example/age.xml
- jar — for loading resources from a JAR file, e.g.:
jar:file:/home/example/example.jar!/age.xml
- http[s], ftp — for loading remote resources using HTTP/HTTPS or FTP protocol, e.g.:
http://example.com/age.xml
Other protocols may also be recognised if your Java runtime supports them.
