-that means that JAXB cannot serialize some of the data structures. Add \r
-appropriate annotations to your data types.\r
-Also check that \r
- - you do not have interfaces to serialize. JAXB cannot serialize them.\r
- - you have a default no args constructor (can be private if you do not need it)\r
- - JAXB cannot serialize a Map, use custom data structure instead!\r
- - Enum cannot be serialized as its abstract class (do not confuse with enum \r
- which is fine)\r
- - Fields serialization leave a little more space for manoeuvre, so use it. If \r
- you do then you can accept and return interfaces, e.g. List, Map; abstract \r
- classes etc, from your methods. \r
- \r
-If you have the data on the server side, but nothing is coming through to the \r
-client, this is a JAXB serialization problem. They tend to be very silent and \r
-thus hard to debug. Check your data structure can be serialized! \r
-\r
-13) Modify the client to work with your new web service. Update Services \r
-enumeration to include new service and ensure that all the methods of this \r
-enumeration take into account the new service. In particular add the service to the \r
-compbio.ws.client.Services enumeration. Modify the getServiceImpl() and getServiceType()\r
-methods. Update the client help text (client_help.txt) and insert it into the Constraints class. \r
-\r
-14) Test the web service with the client. \r
-\r
-15) Make sure the statistics collector works fine with a new web service. \r
-\r
-16) Test on the cluster...\r
+ that means that JAXB cannot serialize some of the data structures. Add \r
+ appropriate annotations to your data types.\r
+ Also check that: \r
+ - you do not have interfaces to serialize. JAXB cannot serialize them.\r
+ - you have a default no args constructor (can be private if you do not need it)\r
+ - JAXB cannot serialize a Map, use custom data structure instead!\r
+ - Enum cannot be serialized as its abstract class (do not confuse with enum \r
+ which is fine)\r
+ - Fields serialization leave a little more space for manoeuvre, so use it. If \r
+ you do then you can accept and return interfaces, e.g. List, Map; abstract \r
+ classes etc, from your methods. \r
+\r
+ If you have the data on the server side, but nothing is coming through to the \r
+ client, this is a JAXB serialization problem. They tend to be very silent and \r
+ thus hard to debug. Check your data structure can be serialized! \r
+\r
+15) Modify the client to work with your new web service. Update Services \r
+ enumeration to include new service and ensure that all the methods of this \r
+ enumeration take into account the new service. In particular add the service \r
+ to the compbio.ws.client.Services enumeration. Modify the getServiceImpl() and \r
+ getServiceType() methods. Update the client help text (client_help.txt) and \r
+ insert it into the Constraints class. \r
+\r
+16) Test the web service with the client. \r
+\r
+17) Make sure the statistics collector works fine with a new web service. \r
+\r
+18) Test on the cluster...\r