Add a result checker to implement operation result processing logic in custom code. The deployed result checker logically validates operation results and produces log records for device clients or the server package log.
Add a result checker when you edit Attribute or Operation properties for a mobile business object derived from a data source. Add a result checker after you have either written a custom one or use a predefined one in Unwired WorkSpace (the latter of which can be configured when you create an object).
Option | Description |
---|---|
Default | The result checker depends on the data source type:
|
None | Return the status as successful with no message. The result checker used depends on the data source type:
|
Custom | Specify a custom result checker. See the topic Writing a Custom Result Checker in the Developer Guide for Unwired Server for information about writing a custom result checker. |
Option | Description |
---|---|
Source folder | By default, this is the Filters folder from your project. Click Browse to locate the source folder for the Java class. |
Package | Click Browse to locate the package for the new Java class. Note: Sybase recommends that you do not leave this field blank. Otherwise, the JDK<version> Java class in the default package cannot be resolved in other packages.
|
Enclosing type | Choose a type in which to enclose the new class. You can select either this option or the Package option, above. Enter a valid name or click Browse. |
Name | Enter a name for the result checker class. |
Modifiers | Select the Java class modifiers. The default modifier is public. |
Superclass |
|
Interfaces |
By default, this is populated with the corresponding interface:
|
Which Method Stubs Would You Like to Create |
|
Do You Want to Add Comments | Select Generate Comments to add comments. From here, you can modify the preferences of the code templates by clicking Configure templates and default values. |