Seams to be a solution. But looks like having a big overhead for
defining mappings.
Did you check the spring modules JCR persistence?
I took a very quick look at it. There should be a decision if we
depend
(partial) on Spring or not. I can't think of any cons now (beside
using
Spring is trendy ;) but some pros:
- we don't have to implement a lot of functionality ourselves
- using Spring could attract more developers
- should be easier and more standardized to integrate functionality
(e.g.
WebServices with XFire)
- the module framework isn't mature yet (deinstalling, runtime
de-/activation), maybe Spring OSGi is a solution
Spring
- we can't use spring in this release (to many changes)
- we are willing to use it in future but we lack a concept
- currently it is not that urgent anymore since the Factory service
we use gives already a lot of flexibility
OSGi
- seams to be an option I will check the specs
- spring osgi
- is m2 and therefore not an option
- has dependencies to other spring parts we would like to keep out
for now
- are the other options (ready to use and free implementations)
Thanks for pushing us ;-)
Philipp Bracher
----------------------------------------------------------------
for list details see
http://documentation.magnolia.info/docs/en/editor/stayupdated.html
----------------------------------------------------------------
