jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Fabián Mandelbaum <fmandelb...@gmail.com>
Subject Re: JCR application design
Date Thu, 26 Apr 2012 10:43:41 GMT
It's up to you to have your business objects manipulate JCR directly
using nodes and properties, or to make your DAO (Data Access Object)
classes that abstract storage (in this case JCR) and provide methods
that use only business objects.

In our application we use this last approach, we have a bunch of DAO
objects, one for each business object, that know how to
(de-)materialize business objects from/to JCR nodes and properties.

On Thu, Apr 26, 2012 at 7:22 AM, decebal <decebal.suiu@gmail.com> wrote:
> Hi
> I have the same question. It's easy to say that no OCM it's the right
> direction but this it's always true only in theory. In applications you work
> with entity/business objects and services, web presentation that "consume"
> these objects. For example in the User entity you have username, password,
> admin flag, ... If you don't use OCM approach you must have a method (in the
> persistent layer, or a jcrhelper) that materialize User object from JCR. I
> think that you must work with business objects (entity) in your application.
> You can use a generic approach using OCM or write by hand a converter from
> JCR Node to User and reverse.
> I want to know how people that don't use OCM works with JCR. How these
> people do business logic and web presentation using only JCR Nodes and
> Properties.
> Best regards,
> Decebal
> --
> View this message in context: http://jackrabbit.510166.n4.nabble.com/JCR-application-design-tp4561691p4589402.html
> Sent from the Jackrabbit - Users mailing list archive at Nabble.com.

Fabián Mandelbaum
IS Engineer

View raw message