On 02/17/2012 04:22 PM, Cooper, Sean D. wrote:
I have an undeveloped idea that I would like to discuss. I have seen several
projects which are leveraging RAVE or want to leverage RAVE but require
injecting domain knowledge into the RAVE container.
For example, I have one project that wants to generate pages for a project
dashboard. In the current model I would have to add a controller to determine
which project has been requested by the user, inject the project model from the
database (which requires adding the project model into the database) and the UI
layer needs to know what this project model looks like in order to display the
information in a meaningful manner.
I think it would be better to create a generic model for this... a seeding
model. Add some configuration items to recognize a given URL path to use an
external REST API for the domain objects (in JSON format?). These domain
objects would be retrieved through the shindig server and handed to the display
layer directly as JSON objects. These objects could be used by the UI layer to
write out the domain specific information without the RAVE container having to
know this data model. We might even be able to pass these JSON data objects
through shindig directly to the gadgets.
-Sean
Hi Sean, your idea is very welcome :)
I'm currently finishing up a proposal which should be able to address at least
some or even a major part of your requirements.
This concerns what we (@Hippo) call a "Context Mapping Engine" (CME), together
with generic 'content' services through a content repository (JCR).
Note: a JCR doesn't necessarily store just 'plain content' but can store, and
dynamically create, domain model objects like maybe fitting your use-case.
I've hinted at this before but until now we never found the time yet to actually
propose and contribute it.
I can't provide the exact details yet, but I expect we'll be ready to discuss
this further (and start doing the 'works' for it) on pretty short notice.
Regards, Ate
