Re: AW: Wicket + CMS
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]
Re: AW: Wicket + CMS
Frank van Lankvelt schrieb: Hi Frank, think we´ve talked at the meetup about that. 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 will the actual delivery be done by a JSP frontend, or a Wicket frontend? And if JSP will be delivering, can we build CMS-agnostic wicket components that could wor as they would in a normal wicket app (wrapped by some plugin adapter of course)? cu uwe -- THOMAS DAILY GmbH Adlerstraße 19 79098 Freiburg Deutschland T + 49 761 3 85 59 0 F + 49 761 3 85 59 550 E [EMAIL PROTECTED] www.thomas-daily.de Geschäftsführer/Managing Directors: Wendy Thomas, Susanne Larbig Handelsregister Freiburg i.Br., HRB 3947 Registrieren Sie sich unter http://morningnews.thomas-daily.de für die kostenfreien TD Morning News, eine Auswahl aktueller Themen des Tages morgens um 9:00 in Ihrer Mailbox. Hinweis: Der Redaktionsschluss für unsere TD Morning News ist täglich um 8:30 Uhr. Es werden vorrangig Informationen berücksichtigt, die nach 16:00 Uhr des Vortages eingegangen sind. Die Email-Adresse unserer Redaktion lautet [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Wicket + CMS
Hi Uwe, 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 will the actual delivery be done by a JSP frontend, or a Wicket frontend? at the moment, we're focussing on JSP. A custom tag library is under development that accesses the repository and allows url mapping. It should certainly be possible to develop a frontend in Wicket; the models that we use to access the repository are easily reused. To embed plugins, e.g. those used by the CMS, does require some support from the environment. The Wicket session needs to provide a valid JCR session, for example. And if JSP will be delivering, can we build CMS-agnostic wicket components that could wor as they would in a normal wicket app (wrapped by some plugin adapter of course)? yes, if you're components don't need to have any interaction with the CMS then this is certainly possible. When you do want to have an interaction, some additional constaints will (likely) be present due to the possible actions of other plugins. If you want to further discuss the Hippo CMS, then we should move the discussion to the hipporepos-dev mailing list. You can subscribe and visit the archives at http://lists.hippo.nl/mailman/listinfo/hipporepos-dev The traffic mainly consists of JIRA updates and svn-logs, but it should be possible to filter these out if you want to. thanks for the interest! cheers, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AW: Wicket + CMS
Someones in this thread have ever seen Riot CMS ?! *Riot is a web-based Open Source Content Management System written in Java. It's quite different from other systems as it has been designed to match the needs of custom applications, [..]* http://www.riotfamily.org I think would be relatively easy to add Wicket support to it. // Paolo On Fri, Apr 18, 2008 at 9:28 PM, Frank van Lankvelt [EMAIL PROTECTED] wrote: Hi Uwe, 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 will the actual delivery be done by a JSP frontend, or a Wicket frontend? at the moment, we're focussing on JSP. A custom tag library is under development that accesses the repository and allows url mapping. It should certainly be possible to develop a frontend in Wicket; the models that we use to access the repository are easily reused. To embed plugins, e.g. those used by the CMS, does require some support from the environment. The Wicket session needs to provide a valid JCR session, for example. And if JSP will be delivering, can we build CMS-agnostic wicket components that could wor as they would in a normal wicket app (wrapped by some plugin adapter of course)? yes, if you're components don't need to have any interaction with the CMS then this is certainly possible. When you do want to have an interaction, some additional constaints will (likely) be present due to the possible actions of other plugins. If you want to further discuss the Hippo CMS, then we should move the discussion to the hipporepos-dev mailing list. You can subscribe and visit the archives at http://lists.hippo.nl/mailman/listinfo/hipporepos-dev The traffic mainly consists of JIRA updates and svn-logs, but it should be possible to filter these out if you want to. thanks for the interest! cheers, Frank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: Wicket + CMS
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]
