I'd say, first settle on the scope. If you talk about CMS components, what exactly do you mean? Like the examples given: rich text components/ components that are JCR aware (and while you're at it, take a look at http://jcp.org/en/jsr/detail?id=283), or do you mean components that have to be able to be deployed in a certain CMS?
And if you talk about Wicket CMS, you are talking about a container like e.g. opencms, Jahia or Apache Lenya or any of http://java-source.net/open-source/content-managment-systems? Those three examples are quite different from each other. For instance, one choice with a big impact - much larger than whether or not to use JCR (which btw I think is a good idea) - is the workflow support you give. The ability to define roles and workflows for content is something you would need for anything serious (and don't build that stuff yourself, but e.g. use jBPM). So I think you should first decide whether you want to build widgets with CMS-like functionality, or whether you want to build a CMS. And if you want to build a CMS, you have a lot of further scoping to do. :) As a final note, a similar project was done at Topicus 3-4 years ago that used/ considered Jakarta Slide (which was the initial playground for JSR 170) and had a prototype that was focussed on content definitions etc. Look it up and see if there's anything to learn (probably a bit outdated by now). Good luck and pls keep us informed, Eelco ------------------------------------------------------------------------- Using Tomcat but need to do more? Need to support web services, security? Get stuff done quickly with pre-integrated technology to make your job easier Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642 _______________________________________________ Wicket-develop mailing list Wicket-develop@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-develop
