Existing code based on COD (orca.cod.* namespace) would still work in Orca 2.0. However, COD is on its way to deprecation and future releases are likely not to include support for it. All existing code that is intended to be used with future releases should be ported to the new code base. This document describes the porting process.
The BEN controller package (orca/controllers/ben) has been updated to use the new API. In particular, the InterdomainController can serve as a reference of how to write a controller that conforms the the new code base.
The basic test is to see if your code still depends on anything from the orca.cod.* namespace. If it does, then your job is not done yet. If not, then you are halfway there. If the code compiles, you are almost there. Some additional testing to ensure that the code still works would complete the process.
What needs to be updated? Any code that resides inside the orca.cod namespace should be replaced with the corresponding code that does not reside in orca.cod. This often means:
Properties passed to handlers may have changed slightly. Since our documentation in this area is particularly lacking, we describe a process that can help with this step: You may want to put a breakpoint in Substrate.getConfigurationProperties and examine the constructed properties list. Once you've identified the names of the properties you are interested in, you can update your handler to reflect the new naming.
If you have a question and need assistance please send an email to the geni-orca users mailing list.