Dear Magnolians

We have announced a magnolia shop module quite some time ago and have passed it 
on to Magnolia. Unfortunately it could not be publicly released so far due to 
two dependencies. 

One of the dependencies is a magnolia module which assists in persisting 
objects to the JCR repository and back. This is needed because the shop needs 
POJOs to handle data efficiently and the Contente2Bean classes are somewhat 
limited. Now instead of reinventing the wheel (which the module to some degree 
did) a smart man at Magnolia asked us to have a look at Jackrabbit OCM. 
Jackrabbit OCM does the same thing (again: to some degree) and seems to be 
doing it well (maybe apart from the fact that it's poorly documented and nobody 
knows exactly what's going on with the Jackrabbit 2 compatible version).

So here's magnolia-module-ocm! It's an integration of Jackrabbit OCM into 
Magnolia with the following "special features" beyond OCM:
- The whole class description configuration is in the config repository instead 
of xml files or code annotations
- The magnolia collection structure is supported (collection node with numbered 
element nodes)
- OCM works with Magnolia's mgnl:metaData nodes (which make the standard OCM 
trip, fall and crash terribly both when retrieving objects from the repo as 
well as when writing object to the repo)
- automatic creation of parent nodes for hierarchical node structures (e.g. 
/n/na/name) is supported
- automatic (numbered) node name generation is supported

You can find more info about the module (incl. download links) here:
http://www.fastforward.ch/web/ff/dokumentation/entwickler/magnolia-module-ocm.html

Once the dependency in the shop module is exchanged we can then finally make 
that publicly available too.

Regards,
-will

----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <[email protected]>
----------------------------------------------------------------

Reply via email to