Before deploying mobile business objects that use custom filter classes, you must copy the filter classes to the Unwired Server.
Manually deploy filters to Unwired Server using these steps. As an alternative, you can add JAR files during MBO deployment using the Package Jars option.
If your Unwired Servers are running in a cluster, you must copy the filter classes to the "primary" server in the cluster. From Sybase Control Center, you can identify which server is the current primary on the left-hand panel that lists your Unwired Servers.C:\workspace.2\549543\bin>jar -cvf testFilter.jar *
added manifest adding: test/(in = 0) (out= 0)(stored 0%)
adding: test/TestFilter.class(in = 3409) (out= 1596)(deflated 53%)
<Unwired-Server-install>\lib\filters\<DeploymentPackageName>
For example, if you have a FilterTest_1.0.0 package with a filter called com.acme.filters.TestFilter, you would create a <Unwired-Server-install>\lib\filters\FilterTest_1.0.0\com\acme\filters\TestFilter.class directory. Or, you can jar up the com.acme.filters.TestFilter class into a acmeFilters.jar file and copy it to <Unwired-Server-install>\lib\filters\FilterTest_1.0.0\acmeFilters.jar.
<Unwired-Server-install>\lib\filters\
Whenever a result set filter is deleted, renamed, or moved (from WorkSpace Navigator for example), all it's references are automatically updated.
The custom classloader for FilterTest_1.0.0. is refreshed during deployment so there is no need to restart Unwired Server.