On Dec 6, 2009, at 6:20 PM, Andrus Adamchik wrote:
> So the next step is to finish CAY-1318 (which is mainly about
> upgrading the old projects to the new format), and to do the switch
> to the new configuration. In terms of public API, I think that most
> of the classes in org.apache.cayenne.conf will have to go. There's
> no point in deprecating them (although I sort of did it in a few
> places already), as the framework will not use them at all. One
> possible interim step is moving all these classes from runtime jars
> to the Modeler, so that the Modeler could read older project files
> and perform needed upgrades. At a later point we may also refactor
> the Modeler to use the new configuration classes, as mentioned above.
I been thinking about this step, and decided against moving o.a.c.conf
to the Modeler. Instead I am going to create a separate new module
cayenne-project-unpublished, implementing project saving/loading
functionality with the Modeler use in mind. Once this is done, the
Modeler and runtime can be switched to the new stack simultaneously,
and o.a.c.conf and o.a.c.project removed from the runtime jars.
IIRC Ari mentioned before that project saving functionality doesn't
have to be in the runtime. This refactoring will do just that.
And one more issue - maintaining the JPA jars is becoming an issue
with the new configuration work, as it uses the old API and will
require special attention. Since we are not working on JPA, I suggest
that we remove it from trunk. It will be preserved in Subversion on
3.0 branch in case somebody decides to resurrect it. Thoughts?
Objections?
Andrus
This archive was generated by hypermail 2.0.0 : Tue Dec 08 2009 - 07:49:38 EST