Hi Niek, > I am researching different CMS applications such as Hippo for > a project to find out which one would be the most suitable. > Someone with experience regarding Hippo told me however that > a new Hippo version will be released. And that this new > release will use a different Repository and use wicket > instead of Cocoon. So that raised the question here whether > that new version will be backward compatible. Could someone > please provide me with more information regarding the new > Hippo CMS version (7 i think) and how difficult it will be to > supplement an older version with this one? Also is it true > Cocoon is out and Wicket is in?
It is true that we will use Wicket as the web framework for the Hippo CMS 7 user interface. This is mainly because of its excellent Java/HTML separation, and pure Java approach to web app development. Cocoon is more of an XML framework than a UI framework :) The new Repository will be bigger and better, and will support the Java Content Repository specification (JSR-170). It also allows for much more finegrained storage of content as objects instead of 'raw' XML files. However, the basic concepts and ideas of Hippo CMS 6 will remain in place, so it's certainly not a complete overhaul. Hippo will do everything to make sure that a new version of our software is backwards compatible with a previous version, or to at least provide a migration path for it. Obviously, we can't guarantee that everyone's extensions and customizations will work out-of-the-box after an upgrade (unless you have a SLA agreement with Hippo for that), but we will give you guidelines on how to migrate. I hope this helps. If you need more information, don't hesitate to email me directly. Also, keep an eye on www.onehippo.com, as we're ramping up for our new release :) Arjé Cahn CTO Hippo ******************************************** Hippocms-dev: Hippo CMS development public mailinglist
