On 11.11.2005, at 14:30, Andrus Adamchik wrote:
>
> On Nov 11, 2005, at 1:54 PM, Boris Kraft wrote:
>> The JSR-170 API abstracts from the actual storage, which is one of
>> the huge benefits. For all our websites and applications based on
>> Magnolia, we can simply switch the backend repository implementation
>> by installing a new version (of Magnolia), configuring to use the
>> repository we like, and then activate the content from one Magnolia
>> to the next.
>
> That's nice, but I guess the point of such flexibility is to allow
> users to select persistence mechanism they want. Is there any plans to
> make it work with PostgreSQL (or any other relational DB)?
Well, you'd have to check with the Jackrabbit project, this is really
none of our business ;-)
I believe that it is straightforward to persist *somehow* into any DB,
the question is what benefit you have if the data-model is crappy.
> Aside from concerns about running a live site on berkley DB,
Tell me more if you wish
> there are a few immediate problems to consider. Even our relatively
> small site (though the traffic can be very high at times) already has
> simple integration needs. A relational database as an integration
> point makes the most sense to me.
Yes but that does not mean that all data has to be persisted to the
same store (database). In your current setup, it is not either, right?
> For instance after some tinkering I was able to setup Confluence to
> use Jira logins. So now Jira is a single place where users can
> register and admins can assign them to groups. I'd like to reuse that
> for any new app we may add. Actually single login problem is probably
> the easiest one to solve as Magnolia may use (does it?) J2EE security.
We recently added JAAS - see
http://svn.magnolia.info/view/magnolia/trunk/magnolia-jaas/
> This is just the feature that we need right away.
Sure thing
- Boris
This archive was generated by hypermail 2.0.0 : Fri Nov 11 2005 - 14:51:26 EST