From graffito-dev-return-251-apmail-incubator-graffito-dev-archive=www.apache.org@incubator.apache.org Tue May 31 11:20:24 2005 Return-Path: Delivered-To: apmail-incubator-graffito-dev-archive@www.apache.org Received: (qmail 17715 invoked from network); 31 May 2005 11:20:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 31 May 2005 11:20:23 -0000 Received: (qmail 91803 invoked by uid 500); 31 May 2005 11:20:23 -0000 Mailing-List: contact graffito-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: graffito-dev@incubator.apache.org Delivered-To: mailing list graffito-dev@incubator.apache.org Received: (qmail 91773 invoked by uid 99); 31 May 2005 11:20:23 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received: from ajax-1.apache.org (HELO ajax.apache.org) (192.87.106.226) by apache.org (qpsmtpd/0.28) with ESMTP; Tue, 31 May 2005 04:20:21 -0700 Received: from ajax.apache.org (ajax.apache.org [127.0.0.1]) by ajax.apache.org (Postfix) with ESMTP id 154F7182 for ; Tue, 31 May 2005 13:20:10 +0200 (CEST) Message-ID: <1731784376.1117538410085.JavaMail.jira@ajax.apache.org> Date: Tue, 31 May 2005 13:20:10 +0200 (CEST) From: "Christophe Lombart (JIRA)" To: graffito-dev@incubator.apache.org Subject: [jira] Updated: (GRFT-25) PROPOSAL : New Graffito Object Model In-Reply-To: <215801854.1117538394562.JavaMail.jira@ajax.apache.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N [ http://issues.apache.org/jira/browse/GRFT-25?page=all ] Christophe Lombart updated GRFT-25: ----------------------------------- Attachment: graffito-model.png Add the UML Class Diagram > PROPOSAL : New Graffito Object Model > ------------------------------------ > > Key: GRFT-25 > URL: http://issues.apache.org/jira/browse/GRFT-25 > Project: Graffito > Type: Improvement > Components: Model > Versions: 1.0-a1-dev > Reporter: Christophe Lombart > Assignee: Christophe Lombart > Fix For: 1.0-a1-dev > Attachments: graffito-model.png > > Introduction > ------------ > This document describes a proposal for a new Graffito Object Model. > In my point of view, the model has the following weaknesses : > 1. The CmsObject interface contains too many attributes. Title, description and owner should be not mandatory. Futhermore, this interface contains getObjects() and getProperties() which could be duplicate attributes. > 2. The Document interface forces to have a binary content. Binary content is only interesting for Document management & asset management. We can expect to use Graffito for a CMS application containing only articles. In a such case, an article can be composed only of a set of String : title, summary, content, authors, ... and not binary content. > 3. The Content interface is not an appropriate name. DocumentStream seems to be more explicit. > 4. We need to have a better internationalisation support. > 5. It is difficult to extend the model. > The New Object Model > -------------------- > The proposed model is splitted into different modules (see in attachement the UML class diagram) : > * The Graffito code module. > * A series of optional modules. > 1. The Graffito Core Module > --------------------------- > This module contains all ancestor objects like CmsObject, Folder, Content. Content is the ancestor of any kind of content object (Document, topic, article, ...). Versionning is not mandatory is all case. The "VersionnedContent" is the ancestor used in a version management context. As you can see, only content can be versionned. Later, we can support versionning on Folders. > 2. Optional modules > ------------------- > Depending on the application requirements, the Graffito users can select one or more optional modules. If the Graffito model doesn't fit to the application requirements, it should be possible to plug a customized module. One subproject per module has to be defined in the Graffito project. > 2.1 Document Management module > ------------------------------ > This module manage any kind of binary documents (Ms Word, pdf, ...). By default, this DM module is supporting internationalisation. In order to increase the performance, the DocumentStream should be defined as a proxy. All documents are versionned. > 2.2 Article Management module > ----------------------------- > This module can manage translated articles or single language articles. All articles are versionned. > 2.3. Forum > ---------- > This module is a simple object model that can be used for a Forum application. Obviously, topic (the forum content) are not versionned. > 2.4. Other modules > ------------------ > Now, it should be easy to extend the Core Graffito module or any other optional modules. For example, someone can add a news management, asset management or customize the article module. > > 3.Open points > -------------- > * Review the project structure in order to support modules. > * CmsObject interface : getProperties, getObjects() : David, are you using both attributes ? > * Internationalisation : providing by default in the different module or not ? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira