Known Issues for Sybase Unwired WorkSpace – Mobile Business Object Development

If both are mapped, the client parameter value is ignored and the personalization key value is used. Unwired WorkSpace may show this warning:

Client parameter 'GENERALDATA' might not be used, 
as the mapped argument has 'Fill from Attribute' or 
'Personalization Key' specified.

Although deployment and code generation succeeds, you may still get a NullPointerException in the server log during runtime and the operation fails on the device.

Workaround: Only map create, update, or delete operation parameters to a personalization key or a client parameter, not both.

Workaround: This is a known Eclipse issue. Remove the following file from the problematic Eclipse workspace, then restart Unwired WorkSpace: <The workspace used in the previous crash>\.metadata\.plugins\org.eclipse.core.resources\.snap.

Workaround: Re-create the JDBC MBO after changing the stored procedure definition in the EIS.

Resource '/<Mobile Application Project name>
/Generated Code/temp_afx does not exist. Resource '
/<Mobile Application Project name>/Generated Code/genfiles' 
does not exist.

Workaround: Ignore the error messages. The objectAPI code generates successfully.

Unwired WorkSpace automatically creates an MBO with old value arguments (for operations) when you drag and drop a database table. If the datasource includes operation arguments with large object types (BigString/BigBinary), Unwired WorkSpace displays a warning message stating the old value argument with large object types are ignored, but the SQL definition generated still includes the old value argument with the large object type.

Workaround: Manually remove any SQL clauses which include old value arguments with large object types.

Workaround: Unmap the "Propagate to attribute" field, which allows you to specify the necessary default values so that the execution to the EIS successfully retrieves MBO metadata.

When adding an operation and corresponding SQL statement, Unwired WorkSpace executes the SQL statement to verify it is correct. Sometimes the return error is not a syntax error but a data error (for example, a foreign key restriction). The EIS API cannot distinguish syntax from data errors and exits the wizard.  

Workaround: Be aware of the EIS schema to which you are binding the MBO. For example, verify that database data is correct, and enter the correct default values so the SQL statements execute correctly.

During deployment, output mappings are automatically generated for Create operations to support multi-level insert operations. The set of generated output mappings may not be the same as the output mappings configured in Unwired WorkSpace for the operation. However, the final set of output mappings is a union of the two sets, so the user-configured output mappings are retained. The MBO developer may see a warning in the output mapping tab indicating that some output mappings are ignored when using the "Apply Output of ENTITY READ" operation cache policy.

Workaround: Ignore the warning since the output mappings are automatically generated during deployment.

Since SAP BAPI operations run asynchronously within the SAP system, the operation may not complete before Unwired Platform attempts to refresh the cache with new or updated results if using the "Invalidate the cache" policy.

Workaround: Do not use the "Invalidate the cache" policy with MBO operations bound to an SAP BAPI.

Workaround: Ignore these errors.

This is due to a known Eclipse 3.7 bug (https://bugs.eclipse.org/bugs/show_bug.cgi?id=355560). In standby mode, the Welcome page is docked to the right as a view in the Mobile Development perspective, since the Problem View is part of the Mobile Development perspective.

Workaround: Double-click the docked Welcome page to extend it to full screen.

For an MBO operation, a non-nullable argument must get its runtime value via one of the following: client parameter, personalization key, default value, or fill-from-attribute. If a non-nullable argument has fill-from-attribute or client parameter already, its default value is ignored. Unwired WorkSpace still allows the user to input a default value.

Workaround: In this case, you need not set the default value, because it is not used during runtime.

When doing preview or test execute in Unwired WorkSpace during MBO development if the data volume is large, for example, either a large number of rows, or a large object in the returned result, Unwired WorkSpace may run out of memory and fail.

Workaround: Do not select Preview or Test Execute with large results, or increase the Java VM argument, -Xss -Xms, and -Xmx in the UnwiredWorkSpace.bat to increase the stack and memory (heap) size.

Invoking File > Save As Image File from the Object Diagram context menu fails if PDF is the image format.

Workaround: None.

The assigned stack size and/or heap size is 
not sufficient for the attempted operation.

Workaround: Increase the stack and heap size of the Eclipse runtime parameter in UnwiredWorkSpace.bat with -Xmx, -Xms, -Xss arguments, or reduce the complexity or nested level of the Web Service definition of the MBO operation.

When using the Code Generation wizard, if you enable the option to generate Javadoc, you cannot generate the code to a folder containing Chinese characters without first changing the language for non-Unicode programs to Chinese.