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]
