You can use web scripts to work with content in the WCM (”AVM”) store. And, you can render dashlets with web scripts (you’d place an r:webScript tag on a JSP page and then tell the dashboard that your dashlet is rendered with that JSP).

If you extend Alfresco’s content model, you should be able to use the web client to modify that metadata. So, I’m not sure what dashlets and web scripts buy you in this particular case unless you are talking about persisting metadata from a web page accessed by users who are not going through the web client.

If that’s the case, dashlets don’t make sense because they only work within the web client. Web scripts without dashlets is a good approach for this kind of thing, though.

Hope that helps,

Jeff

I am new person in the alfresco world. I am working on a project where in I have to use the functionality most of the functionality by WCM but I also I wanted the document management style functionality like attaching meta data to the uploaded documents in a website.

We were able to decide we could do this using the dashlet functionality that is available and then then calling some functional web scripts web scripts which will be extending the content model for.

I was wondering if had nay suggestions regarding the same.

Thanks,
Gaurav

interesting post. 2 comments though:

Re JCR and Atom: David Nuescheler has written a post about this topic that might be of interest for you.
http://dev.day.com/microsling/content/blogs/main/jcr-loves-atom.html

Re coarse and fine-grained APIs: Sling comes with support for JSON out of the box. Calling parties can specify the number hierarchy levels they want to retrieve.

Cheers
Michael

I think you shouldn’t look farther then Atom Publishing Protocol. Atom with extensions (which are part of the specification) covers pretty much all you need to support restful content services. And base on what other vendors are doing (e.g. IBM Quickr) it looks like emerging content API standard.