jackrabbit-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Staudinger <robert.staudin...@salzburgresearch.at>
Subject Re: Specialised SQL Backend
Date Fri, 14 Apr 2006 16:57:35 GMT
Stefan Guggisberg wrote:
> hi rob,
> On 4/13/06, Robert Staudinger <robert.staudinger@salzburgresearch.at> wrote:
>> Marcel Reutegger wrote:
>>> Hi Rob,
>>> I'm not sure if that is of any help, but you could use an EventListener
>>> to get notifications about changes in the workspace and then trigger
>>> your indexing process.
>> Oh, there seems to be a misunderstanding. I want to use an SQL backend,
>>   RDBMS usually don't need any active indexing triggering/management
>> from outside on their tables.
>> Having slept over my original post i think the question is more like
>> "Would it be possible to hack an SQL backend that allows for the storage
>> being optimized towards the application by using indices and
>> distributing tables in a favourable way".
> sure, you could *hack* your own application specific db persistence manager
> for your purposes. but you have to be aware that this approach is not
> officially supported by jackrabbit which is designed to support arbitrary
> node types/structures. future changes in jackrabbit could break your code.

Continuing my search for how to extend jackrabbit in a supported and 
forward compatible way I came across the node type registry interface. 
Is this the recommended way for enforcing application specific schemas? 
Having custom nodes also seems like a clean way to me letting an app 
specific PM know about preferred storage and indexing requirements.
Or am I completely off track?


View raw message