jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guo Du <mrdu...@gmail.com>
Subject Re: [jr3] Plugin architecture
Date Thu, 18 Feb 2010 11:54:48 GMT
On Thu, Feb 18, 2010 at 10:02 AM, Bertrand Delacretaz
<bdelacretaz@apache.org> wrote:
> Do you really think Jackrabbit should allow its core plugins to go
> away at runtime?
No, it's just one of OSGi feature doesn't need here.

> i don't mind providing osgi support at a higher level, the core however
> should IMO not have any osgi-dependenciesi.
+1
I would prefer to have our core implementation based on bean style
pojo class. Thus we can have xml, OSGi, war, spring or whatever
container to assembly for final runtime.

> First of all, I would define an API for configuration changes. This
> API could be the regular JCR API, and the configuration could be
> stored in special "system" nodes.
There are two kind of configuration apart from user data:node
definition and repository definition.
It's good to store node definition inside the repository and api to
manage changes. But the repository configuration shouldn't go inside
repository. Think about store db connection username/password inside
repository.

> Extensibility of the importXML and exportDocumentView methods come to mind.
It may worth to redefine how we import/export. Xml should just be one
of format we support. I am not confident to use xml to export/import
GB/TB size data. ContentHandler could responsible for how the data
should be export/imported.

-Guo

Mime
View raw message