Mailing-List: contact chemistry-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: chemistry-dev@incubator.apache.org
Message-ID: <1339161200.235121265993488091.JavaMail.jira@brutus.apache.org>
Date: Fri, 12 Feb 2010 16:51:28 +0000 (UTC)
From: "Florent Guillaume (JIRA)" <jira@apache.org>
To: chemistry-dev@incubator.apache.org
Subject: [jira] Commented: (CMIS-114) APPObject's lack APP specific typesafe
 methods
In-Reply-To: <1533169474.199521265856749237.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/CMIS-114?page=3Dcom.atlassian.j=
ira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D128330=
68#action_12833068 ]=20

Florent Guillaume commented on CMIS-114:
----------------------------------------

First, about the design: Chemistry has nothing to do with JCR. You say "one=
 would initially hope the JCR API could serve as that single general purpos=
e repository API" but that's not the case. The JCR domain model is differen=
t, and the Chemistry API is designed to be focused on CMIS, nothing else. T=
here are no references to JCR in it.

If you *know* you have a JCR somewhere behind then yes you could use the JC=
R APIs directly, but then you're not using CMIS anymore.

The only two level of abstractions in Chemistry are:
1. high-level (Connection, Document, Folder, etc.),
2. low-level (SPI, ObjectEntry).

Before closing this bug, I'd like to know what AtomPub-specific information=
 (which links for instance) you want to get from the entry =E2=80=94 maybe =
some is already available in a way you don't know about, or maybe it's some=
thing legitimate that hasn't been added yet.


> APPObject's lack APP specific typesafe methods
> ----------------------------------------------
>
>                 Key: CMIS-114
>                 URL: https://issues.apache.org/jira/browse/CMIS-114
>             Project: Chemistry
>          Issue Type: Improvement
>          Components: atompub
>            Reporter: Chris Hubick
>            Priority: Minor
>         Attachments: chemistry_app_type_safety.patch
>
>
> Hi.
> When using APPContentManager to communicate with my repository, I would l=
ike to use the APPObject derived API's, in order to access underlying APP s=
pecific information (Link's, etc).  The problem is that I end up writing a =
lot of code containing ugly object cast's like this:
> APPContentManager contentManager =3D new APPContentManager("");
> APPRepository repository =3D (APPRepository)contentManager.getDefaultRepo=
sitory();
> APPConnection connection =3D (APPConnection)repository.getConnection(null=
);
> APPFolder aFolder =3D (APPFolder)connection.getFolder("");
> When I would rather have the ability to write typesafe code like this:
> APPContentManager contentManager =3D new APPContentManager("");
> APPRepository repository =3D contentManager.getDefaultAPPRepository();
> APPConnection connection =3D repository.getAPPConnection(null);
> APPFolder aFolder =3D connection.getAPPFolder("");

--=20
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.