>From: <[EMAIL PROTECTED]> > > Hei > > If we where to look into a better configuration control, I would suggest > taking > a close look at Apache Jackrabbit (JSR-170). This gives among a lot of good > things, versioning. You can even run with (Embedded) Derby as a backend, or > just > a plain XML structure if you prefer. I have been testing it for the last > couple > of weeks as a possible storage for a web application. During this testing, it > struck me that the configuration in Shale/Clay might be a good candidate for > this. I guess I would have to rewrite the Configuration handler to read its > data > from this new store. One of the nice features in Jackrabbit is the > possibility > to have listeners on it, meaning one would be able to reconfigure Shale "on > the > fly" so to speak through a GUI quite easily. >
Ya, that would be a great marriage. I'm not sure what the interface would look like but I suspect it would be just snapping in a abstraction of a resource resolver? >From a web application, how would you specify a label or correct version? I >guess I need to take a look at jackrabbit so I can ask better questions. If this is an itch you need to scratch, I'll help out in the refactoring. This type of integration might give Clay a new facet for not only creating reusable view fragments but also providing a interface to manage them within the product life-cycle. Gary > Hermod > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
