Consultor Eletrônico

Applies to Apptivity Runtime 2.1 and above.

SUMMARY:

The methods, abServer.clientRequest() and abServer.notifyClient(), are
used for communication between the client and server. For either of
these methods, passing a value of null in any parameter will cause
the values of all subsequent parameters to be effectively null.

EXPLANATION:

For both of these methods, passing a null in any parameter prevents all subsequent parameters from being sent. On the server side, the
parameters are packed into a vector and sent to the client. The client unpacks the vector and presents the objects separately to the event handler. If the server were to ignore the fact that one parameter was null and still send the subsequent parameter(s), the client unpacking the vector would see only the non-null values, and assume incorrectly that these were the first n consecutive parameters. The value(s) of any subsequent parameter(s) would be taken to be null.
Instead, the design decision was made not to send any remaining
parameters once a value of null was encountered.

SOLUTION:

One way around this is to pass an abNull instead of null for Object
parameters.


References To Written Documentation:

Apptivity 2.1 Online Help on class abServer
Apptivity 2.1 Developer's Guide Chapter 16 - Events and Event Handlers
Apptivity 3.0.x API Reference accessible via Online Help
Apptivity 3.0 Developer's Guide Chapter 17 - Events and Event Handlers