Hi, that is correct, Hippo CMS 7 should be ready for release in a few months time. It is a rewrite where the CMS itself is implemented in Wicket.
<plug shameless="true"> The repository is a JCR (JackRabbit) repository extended with workflow and faceted navigation. The CMS is composed as a set of plugins. These Wicket components can be configured and that can be dynamically swapped in and out of the application. We use this for example for the templates. Templates consist of a set of (template) plugins and a configuration in the repository. The template configuration can be edited in the CMS itself! </plug> At the moment we're rethinking the architecture, so I can't give details on how plugins are implemented or how they are linked together at runtime. cheers, Frank On Thu, 2008-04-17 at 14:12 +0200, Noz, Felix wrote: > Hi, > > I've also read about plans to use wicket integration in Hippo Cms and I will > keep an eye on it. I've also managed to access OpenCms content with wicket > but because we have a lot of JSP that we would like to reuse and we > contemporary need a solid frontend framework integration we will - as a start > - concentrate on a classic rerquest-based one with jsp view for now. Maybe we > will recur to wicket again later. > Thanks for your and all other people's answers. > > Regards > > Felix Noz > > > > -----Ursprüngliche Nachricht----- > Von: StephenP [mailto:[EMAIL PROTECTED] > Gesendet: Mittwoch, 16. April 2008 11:57 > An: users@wicket.apache.org > Betreff: Re: Wicket + CMS > > > Our project has tied in HippoCMS for pulling a portion of content into wicket > pages. > I don't have many details to hand but it wasn't too hard. > Hippo has a xml over http interface that we use to cache content, before > putting the xml elements into wicket models. > > We are using hippo version 6, but I think hippo version 7 (the next version) > will be using wicket internally. I don't know if this will allow any stronger > integration with a wicket app. > > > > > > Noz, Felix wrote: > > > > Hello everybody, > > > > I'm currently evaluating different Frontend Frameworks to use them > > with a Java-Based CMS (OpenCms) and I'm very interested in trying > > wicket. The CMS has got its own Template mechanism which is based on > > JSP. Because it would be a problem for us to throw away all existing > > Templates and JSP Tags my idea was to implement a > > ResourceStreamLocator that connects to the CMS via http and delivers > > the resources directly from the CMS so that the CMS is rather a pure > > persistence and template system. > > My questions are: > > > > - Is this a passible way to connect wicket to a jsp based system? > > - Are there any better solutions? > > - Does anybody else has experience in connecting OpenCms + wicket? > > > > Regards > > > > i.A. Felix Noz > > > > ______________________________________________________________________ > > ______________ > > > > Felix Noz > > Junior IT-Berater > > Dipl. Informatiker (FH) > > > > comundus GmbH > > Schüttelgrabenring 3, 71332 Waiblingen > > > > Telefon +49 (0) 71 51-5 00 28-22 > > Internet www.comundus.com > > > > Geschäftsführer: Klaus Hillemeier > > Amtsgericht Stuttgart, HRB 264290 > > > > comundus ist ein Unternehmen der IT EXCELLENCE Group. > > ______________________________________________________________________ > > ______________ > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > -- > View this message in context: > http://www.nabble.com/Wicket-%2B-CMS-tp16696564p16720234.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
