hi guillaume, > We are working on a full portal solution, including an innovative jsr168 > portal engine and a set of content oriented applications (online content > publication, document management, workgroups, discussion spaces). The > portal engine uses the JCR to store it's structure and user preferences. excellent. i think a content repository is an excellent choice for that ;) hierarchical and all ;)
> Of course, most of our applications store their content into JCR too. cool. > We are using Jackrabbit as a JCR implementation and we are very happy > with this one. great to hear. > One of our customer will soon switch into production environment and we > want to backup/restore the data store easily. > Another point is that when customers ask how data are stored, I think > they will be more confident if we answer 'into a berkeleydb database' > than 'directly on filesystem'. (However I think it should not be a > problem to store them directly in a descent filesystem in production > environment). ;) > A part of our portal solution will be opensourced soon. looking forward to that... thanks for all the infos, it is great to hear about good applications of jcr. regards, david
