[Aplaws-devel] [aplaws - Developing on APLAWS+] RE: hibernate and Aplaws

[Aplaws D. L. <apl...@li...>]

Read and respond to this message at: 
https://sourceforge.net/forum/message.php?msg_id=7451067
By: pboy

Francois,

|  would it mkae the roadmap easier to move from RedHat persistence to Hibernate
|  and then from Hibernate to JCR

personally I have a slight preference to that route. If we move directly to
JCR we have not only to rework and clean up the class hierarchy, the deprecated
parts of the code, and all the unfinished work spreaded over several packages,
but also to *redesign* large parts of the code as we move from an object relational
persistence to a sort of hierarchical persistence. To perform all of that work
in one step has - mathematically spoken - a lot of "degrees of freedom", may
be to much, and carries the risk to evolve into an unmanageable, insolvable,
never ending process.

Hibernate is an implementation of the Java Persistence API, which inherited
the basic design from the JDO framework which in turn has very similiar design
principles as CCM persistence (which may be seen as a first draft of JDO). The
migration process is better foreseeable and will result rather soon in a working,
improved, and easier maintainable code base. A large part of the work is a quite
mechanically refactoring, some sort of boring but very likely to be performed
in a short time frame.  From that level it is easier and better managable to
migrate to JCR if we decide to do so.

And: Currently nobody made a detailed analysis, whether JCR meets all the
requirements of APLAWS's feature set or what changes are necessary. Given the
current code state it is very difficult, perhaps impossible, to make such an
analysis.


Just my thoughts.

Peter




______________________________________________________________________
You are receiving this email because you elected to monitor this forum.
To stop monitoring this forum, login to SourceForge.net and visit: 
https://sourceforge.net/forum/unmonitor.php?forum_id=368401