EnkiToDo

This page is a place to put larger scale "to do" items.

UML 1.4 / MOF 2.0

• Integrate UML 1.4 model into "ant test"
  • Write unit tests that use this model and exercise the interesting bits (e.g., clustered imports).
• Move to updated versions of MOF/JMI/UML/XMI; see amof for a potential base we can use to help with this

Documentation

• More detailed configuration documentation
  • Pointers to Hibernate and Netbeans config information

Transient Repositories

• Transient Packages
  • Flesh out Enki/Hibernate transient package implementation, using Enki/Transient's code gen as a guide (possible refactoring of common code)
  • Add a transient package to the sample model (for testing and to avoid breaking code gen changes)
• Enki/Transient MDR Events API
  • Basic outline of the necessary changes:
    • Determine all locations where events should be created (probably using Enki/Hibernate codegen as a guide)
    • Add code to create and enqueue the events with the TransientRepository instance
    • Add EnkiChangeEventThread instance to TransientRepository and use it to schedule events
    • Consider refactoring HibernateMDRepository to make the "listeners" collection and actual event firing in enqueueEvent part of a super class or utility class.

Hibernate

• Upgrade to newer Hibernate, and clean up thirdparty directory and redistribution (including license files for all packages)

Little Bits

• Make code gen throw if a variable name is empty.
  • For example, if an association end has no name it current generates methods which have no var names.
  • Probably should take a pass through and add checking for more things like this. They're currently caught later by javac.
• Debug mode which minimizes usage of proxies
  • Hibernate has an option pre-instrument classes, which should elminate proxies.