I don't think JCR should be handled by a plugin. It should be part of core
framework.
And, while at it, I don't think it should replace all Content component
(notably all its data model, and more anyway).
It's just a better way to handle content repositories (JCR = Java Content
Repository
+1
Thanks Anne, easier when neat :o)
Jacques
Anne wrote:
Keep in framework +1
Remove from upcoming release +1
Part of core eventually +1
I think it is (should be) central to content handling, and OFBiz core needs
to handle content. Therefore it should be in core.
Cheers,
Anne.
On 22 March
Re 1: keep in framework +1
Re 2: remove from upcoming release 12.04 +1, remove from all upcoming
future releases until 3 is finished
Re 3: draft up requirements for content framework replacement +1
Excellent roadmapping ;-)
Regards,
Pierre
Op 20 maart 2012 11:48 schreef Jacopo Cappellato
Le 21/03/2012 11:45, Pierre Smits a écrit :
Re 1: keep in framework +1
Re 2: remove from upcoming release 12.04 +1, remove from all upcoming
future releases until 3 is finished
plugin could really be the solution, because most of contribution coming
from customer project, and it's easier for a
From: Olivier Heintz holivier.lis...@nereide.biz
Le 21/03/2012 11:45, Pierre Smits a écrit :
Re 1: keep in framework +1
Re 2: remove from upcoming release 12.04 +1, remove from all upcoming
future releases until 3 is finished
plugin could really be the solution, because most of contribution
Keep in framework +1
Remove from upcoming release +1
Part of core eventually +1
I think it is (should be) central to content handling, and OFBiz core needs
to handle content. Therefore it should be in core.
Cheers,
Anne.
On 22 March 2012 05:04, Jacques Le Roux jacques.le.r...@les7arts.comwrote:
New thread for only JCR funstion
Summary of initial discussion:
Jacoppo:
N) framework/jcr: move back into the Jackrabbit branch until the work is completed and
can replace the existing content framework
Hans:
Also moving the JCR function out is not a good idea however when not
improved
On Mar 20, 2012, at 10:15 AM, Olivier Heintz wrote:
New thread for only JCR funstion
Summary of initial discussion:
Jacoppo:
N) framework/jcr: move back into the Jackrabbit branch until the work is
completed and can replace the existing content framework
Hans:
Also moving the JCR
Or alternatively we could:
1) keep it in framework
2) but remove it from the upcoming new release branch 12.04
3) and then, as a community, we could start the effort (i.e. top priority for
upcoming contributions/commits) of defining the set of requirements needed by
the applications to replace
Le 20/03/2012 11:48, Jacopo Cappellato a écrit :
Or alternatively we could:
1) keep it in framework
2) but remove it from the upcoming new release branch 12.04
3) and then, as a community, we could start the effort (i.e. top priority for
upcoming contributions/commits) of defining the set of
Hi,
1) keep it in framework
+1
2) but remove it from the upcoming new release branch 12.04
+1 - for now the JCR implementation provide the the developer an API
which helps to create, read, update or delete content in the
repository. We have no integration in other (i.e. the content)
Sounds like a plan
Jacques
From: Sascha Rodekamp sascha.rodekamp.lynx...@googlemail.com
Hi,
1) keep it in framework
+1
2) but remove it from the upcoming new release branch 12.04
+1 - for now the JCR implementation provide the the developer an API
which helps to create, read, update or
From: Nicolas Malin malin.nico...@librenberry.net
Le 20/03/2012 11:48, Jacopo Cappellato a écrit :
Or alternatively we could:
1) keep it in framework
2) but remove it from the upcoming new release branch 12.04
3) and then, as a community, we could start the effort (i.e. top priority for
13 matches
Mail list logo
