|
| "DONE" |
Cayenne Modeler Improvements
Consolidate DbEntity/ObjEntity Views
Consolidate the DbEntity/ObjEntity views in Cayenne Modeler so the information is easier to see (more like EOModeler). This will make editing and viewing models much easier, especially with large models, since the current approach requires a lot of scrolling to see everything.
AutoSync
| "DONE" Add a preference to allow auto-synchronization of DbEntity changes into the ObjEntity. |
Modification Tracking
Have the modeler better understand which ObjEntities have been updated since the last code generation cycle and auto-select the "dirty" classes by default.
JavaDoc
Allow JavaDoc to be entered into the model to be output in the generated Java classes. (Andrus) see CAY-400 Jira Issue
Password Encoding
| "DONE" Add extra password encoding options to the modeler per Jira Issue 642. See Password Encoding for more information. |
Cayenne Model Improvements
Change Model Filename
Allow for models that are not named "cayenne.xml". This would accomplish two things:
- More complex/layered applications could be constructed. One team could be creating and maintaining an Authorization framework and administration application while other teams could be creating web applications that use the Authorization framework while connecting to their own separate databases/models. The current version of Cayenne will only load one "cayenne.xml" by default - the first one it finds in the Java CLASSPATH.
- XML is too generic of a file extension. It doesn't associate well with Cayenne Modeler. If you had models named Authorization.cayenne, then the ".cayenne" extension could be associated with Cayenne Modeler via an OS's extension mapping features and allow for double-clicking on the model name to open it up in Cayenne Modeler.[mlk: Actually, I'd rather see .cayenne.xml so it opens as an xml file in non-cayenne-aware editors, but maybe that won't help on some operating systems.]
This change would also require changes to Cayenne Modeler to support saving with different names.
Link Unregistered DOs
Cayenne 1.2 has made things a lot easier by allowing an unregistered DO to be linked with a registered one. In this case, the unregistered one is registered with the DC of the DO it is linked with. It would be very useful if two unregistered DOs could be linked and then when one is registered with a DC, it cascades down the whole object graph. The DOs could then truly be treated as POJOs and all the persistence stuff centralized to one part of the program, rather than being interspersed throughout.
Memory management
It would be nice to be able to have more control of the memory usage.
- Streaming blob/clob. It should be possible to not cache blobs. CAY-316
- Be able to have different level of caching for different tables.
DbEntity / ObjEntity mapping enhancements
Add the ability for users to define regexes to manipulate field names, table names, etc when syncing or importing a database. This was discussed in the mailing list:
http://www.objectstyle.org/cayenne/lists/cayenne-user/2005/11/0090.html
May be nice to abstract this even further with a mapping class, which would be a RegexMapper by default. This way, users could get total control if they happen to need it.
