It should be nice to collect the different JCR/Jackrabbit experiences and
make a JCR design pattern catalog (web, simple app, ...).
Maybe in the wiki ? It will take a lot of time but we can start with small
pieces of info and when someone want to share its experience, it can add
more info in this catalog. If we have different point of view, it will also
help to compare the different solutions.
br,
Christophe
On 6/20/07, Jukka Zitting <[EMAIL PROTECTED]> wrote:
Hi,
On 6/20/07, Hendrik Beck (camunda) <[EMAIL PROTECTED]> wrote:
> > > work directly with too many jcr method calls like
> > > getProperty()/setProperty(). I definitely like the OCM tool, but i
feel
>
> IMO that's the point. In general I would tend to go with Jukka's
suggestion
> and use the JCR API as far as possible. But especially with JSF you
can't
> really use it. JSP + JSF EL aren't powerful enough to use
> Node.getProperty("myProperty") or Iterators or things like that. So you
have
> to put something on top, wrappers around JCR objects or a business layer
> that accesses the JCR API and provides and relatively plain
getter/setter
> API for your web pages.
This is actually something I'd like to see OCM to help with. There was
brief related discussion on the Graffito mailing list a few months
ago, see especially:
http://mail-archives.apache.org/mod_mbox/incubator-graffito-dev/200702.mbox/[EMAIL
PROTECTED]
BR,
Jukka Zitting
