a few of us have been quietly working on a wicket/jcr cms called Brix for a while now. it is almost at a point where we are ready to release a beta, just waiting for wicket-m3 build to go official. in the meanwhile, if you are not afraid of building from source and want a sneak peek, you can check it out here [1].
brix is more of a cms framework/library than a full blown cms. it is designed to be integrated into wicket applications that require cms functionality as part of their feature set. for example, at my company we have built a set of ecommerce tiles (brix tiles are dynamic components that can live inside a cms page) that allow us to build webstores on top of brix. brix includes a url coding strategy (which will hopefully become part of wicket 1.5) that allows for stateless pages as well as url contribution from tiles and query/indexed parameter mixtures. it has been designed with scalability in mind although we have not yet built a caching solution, nor tested if one is necessary. to hopefully preempt some common questions: brix uses a simple plugin system to allow extensibility. we did not use osgi because our time is limited and running wicket inside osgi or osgi inside wicket is not straight forward yet. will we switch to osgi later? maybe. we did not use spring because we did not need the overhead and spring's jcr support is broken because its jcrsessionfactory does not support multiple jcr workspaces so we would have to roll our own anyways. suggestions, feedback, etc are welcome as well as any help. we have not been working on this very long so it is not extremely polished yet. for more info see the website. [1] http://brix-cms.googlecode.com -igor --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
