PoC Assembly - TopCoder Competition Engine - Replace Custom Serialization With Standard Java Serilaization Part 2

Project Overview

TopCoder Competition Engine is a system used for Single Round Matches (SRM) and Marathon Matches (MM). 

Competition Task Overview

The TopCoder Competition Engine is consistuted of several parts, like farm deployer, farm controller, listeners, jboss, clients. It is using a custom serialization approach for decade.

We are wondering if we can replace it with standard Java serialization.

Previously in PoC Assembly - TopCoder Competition Engine - Replace Custom Serialization With Standard Java Serilaization Part 1, we have made the initial changes for make the arena applet work with standard Java serialization.

For this challenge, we'd like to keep on replacing with standard Java serialization.

Following are the scope:

1. For classes that implements com.topcoder.shared.netCommon.CustomSerializable , remove the implementation as in Part 1.

2. Remove the dependencies for custom-serialization sub-project.

3. Make sure the three clients (Arena applet, MPSQAS client and Admin Tool) and the corresponding listeners are working properly with Standard Serialization.

4. Figure out what is changed for mysql database after replacing with Standard Java Serialization, your report should be about which tables, which fields, what is the old format, and what is the new format, so we can write a utility method to covert that.

Winner Responsibility

Winner will be responsible to create pull requests for merge, branches will be created in final fix phase.

Arena VM Usage

Before asking your own VM, you need to have a public key on your profile before asking for the VM.

You can find more details on how to generate a key http://apps.topcoder.com/wiki/display/projects/Generate+SSH+Key and how to connect using it http://apps.topcoder.com/wiki/display/projects/Connect+Using+SSH+Key.

Please reference http://apps.topcoder.com/wiki/display/docs/Competition+Engine+VM+Setup for general usage.