You are correct, at this point you cannot use the OpenAccessDataSource with the new OpenAccess version as now we do not generate the required ObjectScopeProvider class. This is just temporary though, the reason for not having this functionality is that we did not have the time to develop it for the Q1 release. Nevertheless, we will make the required improvements very soon so the OpenAccessDataSource works with the new "context" class. This will be available in the soon-to-come service pack release.
Regarding the context/scope management question, I can tell you that the rules basically apply for both objects e.g. the best practices that you have probably read about scope management also apply for the context. It is just a different API that will expose much more functionality as the time goes by(integration with WCF services, RIA services etc..). It also targeted mostly for customers that have previously used Linq To SQL so they meet a familiar API that cuts the learning curve with OpenAccess.
The persistent classes are not designed for serializing and passing through the wire so it is not recommended to used them directly for WCF calls. The preferred approach for now is to use proxy objects that would transport your data. If you are determined to use WCF, you can review this solution. It should give you some pointers but bear in mind that it is built using an older OpenAccess version, that is through the old wizards. Nevertheless the proxy objects approach is shown in a working scenario which should be enough for you to move ahead using the new version as well.
Please do not hesitate to contact us if you need any more questions or suggestions for us.
the Telerik team
Do you want to have your say when we set our development plans?
Do you want to know when a feature you care about is added or when a bug fixed?
Telerik Public Issue Tracking
system and vote to affect the priority of the items.