Client system services
- Rob Gagne (Unlicensed)
Client system services are APIs available on the client that you can call programatically or as an event handler or method argument through XML. You can call system services as event handlers or method arguments similar to calling an MCO; however, system services do not require the "mco://" prefix.
The following example calls display service from XML:
onCommand="DisplayService.loadStyleSheet( 'mySheet.xss' )"
The following example uses XPathService as an argument:
onCommand="mco:myMco.do( XPathService.evaluateAsString( '/text()' ) )"
Services available on the client are registered with their class names as their registered name in the SystemContainer. See Javadoc for information on each service.
The following table provides a brief description of the client system services:
| Service | Description |
| DisplayService | Provides component sizes and locations, image capturing and other display information and manipulation. |
| PrintService | Provides printing support. |
| NetService | Provides network-related methods. |
| TypeConversionService | Provides the ability to convert objects from one type to another. |
| JavascriptService | Provides the ability to call Javascript defined in the HTML that houses the Nexaweb applet. |
| SoundService | Provides sound-playing method. |
| XPathService | Provides XPath calls that can be made declaratively. |
| DataService | Provides data binding methods, available with the data plugin. |
| New system | Level objects can be created by adding the to the system container, available through the ClientSession interface. |