Hi Ari, For me it is two primary things:
1) The ObjectContext. Our data has a top-level item which faults in up-to tens of thousands of child records throughout a complex object graph. The UI allows editing of the entire object graph and navigating around the various levels. At the end, a single objectContext.commitChanges() persists everything that has changed. This works amazingly well and requires no additional code on our part to manage the object graph changes, re-attach objects to sessions, etc. 2) Cayenne Modeler. I have it open most of the time I'm doing work that touches the Cayenne graph. It is much easier for me to visualize Cayenne objects in CM than Eclipse/etc. It is also quite easy for novice Cayenne developers to run CM and get a gentle introduction in a nice visual format without having to learn annotations or XML. This greatly improves real productivity while they are becoming familiar with the framework. mrg On Mon, Oct 9, 2017 at 3:32 AM, Aristedes Maniatis <[email protected]> wrote: > We are currently rebuilding the Cayenne website and would like to refresh > its unique selling points. What is it that brought you to Cayenne and kept > you here? I know there are some EOF escapees who are here because EOF is no > longer supported, but what positive reasons keep you here rather than > moving to a JPA or other library? > > This is not about denigrating the alternatives but highlighting what > Cayenne does well and showing new developers why they should try it. > > 1. If you made a bullet list of your key features (even with only one > item!) what would it be? > > 2. If you met a developer at a conference and suggest they try Cayenne, > what would convince them to try it? > > > Ari > > > > -- > --------------------------> > Aristedes Maniatis > GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A >
