ApiCompanyScope versus CompanyScope http://developer.cisco.com/c/message_boards/find_thread?p_l_id=&threadId=5816366 2013-05-19T03:22:14Z 2013-05-19T03:22:14Z John Yontz http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=5816398 2012-06-04T23:44:47Z 2012-06-04T23:43:16Z

For enums that are exposed by the API, we define API-specific definitions that are independent of the back-end representation in the database. We do this primarily to guarantee backward compatibility. In this case, ApiCompanyScope is the enum exposed in the API but CompanyScope is what we use in the back-end. Suppose we add another value to CompanyScope called "XYZ" in an upcoming release. We don't want to unknowingly expose this in the WSDL for any clients that are operating in backward compatibility mode. By having a separate ApiCompanyScope, we have tight control over what we expose, and furthermore, we can define any necessary adaptation logic. This also implies we can have separate ApiCompanyScope definitions for each release. In short, for now CompanyScope and ApiCompany scope have the same values. But if they diverge at all on the back-end, we won't automatically break any backward compatibility.

John Yontz 2012-06-04T23:43:16Z Michael Nelson http://developer.cisco.com/c/message_boards/find_message?p_l_id=&messageId=5816365 2012-06-04T23:21:19Z 2012-06-04T23:21:19Z

We recently installed the pre-FCS of CTX 1.1. With that install we noticed a new file ApiCompanyScope.java. It looks to be the same as CompanyScope. Are there any recommendations or guidence regarding these files?

Michael Nelson 2012-06-04T23:21:19Z