Sent by Rickard_Öberg on 21 November 2003 07:07
Hi!
I work for a Java CMS vendor, and we are considering implementing JSR
170 (Java Content Repository). If any of the other vendors are
interested, I'd like to discuss the merit of this JSR, and when/why one
would implement it.
In the spec itself they describe a situation where a large
company/organization have many content repositories (CR), which they
want to be able to access for various reasons. In this case JCR would be
a good API for doing so.
However, are there any reason for a CMS vendor with mostly smaller
organizations to implement it? If there is only one CMS in place, and
typically that is the case for smaller, or even medium organizations,
what are the possible use-cases for it?
Here are some ideas I can see:
* Writing portlets (JSR168) that access and present content using only
standard API's.
* Generating reports that the CMS itself does not provide.
* Inserting content from another backend source, like a database.
etc.
If possible, I would like to know how other vendors view this JSR, and
it'd also be great to know what end-users(/admins) think of it.
regards,
Rickard, a Java CMS vendor
--
http://cms-list.org/
please trim your posts.
