Mailing-List: contact jspwiki-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jspwiki-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of Janne.Jalkanen@ecyrd.com
 designates 193.64.5.122 as permitted sender)
Mime-Version: 1.0 (Apple Message framework v753)
In-Reply-To: <1202230198.25185.822.camel@netframe>
References: <D33B3461-FFD5-4DAD-BFB0-BD5D881B0CFB@ecyrd.com>
 <15cc92000802041303t79962f10qb667039ed434255e@mail.gmail.com>
 <BC499D3C-709E-48E7-A418-9CF8B658F687@ecyrd.com>
 <47A7826E.9070408@altheim.com>
 <439D49D0-58C1-45E4-AD4A-BED94B0F79C0@ecyrd.com>
 <47A7E2D3.2080605@altheim.com> <20080205125535.GA2183@ecyrd.com>
 <47A85EED.3080702@altheim.com> <20080205131340.GC2183@ecyrd.com>
 <47A861E3.90602@altheim.com> <44DA2525-4EEC-496D-93DB-0829C47008CB@ecyrd.com>
 <1202230198.25185.822.camel@netframe>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <BB3FE06C-E962-485F-87FF-F6FEE938BE53@ecyrd.com>
Content-Transfer-Encoding: 7bit
From: Janne Jalkanen <Janne.Jalkanen@ecyrd.com>
Subject: Re: JSPWiki 3 design notes
Date: Tue, 5 Feb 2008 18:58:14 +0200
To: jspwiki-dev@incubator.apache.org


The JDBCProvider could be relatively easily ported to the new API, or  
you could just switch to Jackrabbit and their JDBC provider.

I think you will like it.  The current FileSystemProvider is roughly  
the same complexity as the old one, and *that* has to figure out how  
to store arbitrary metadata.

There needs to be a migration tool though.  I'm *hoping* that the new  
providers are able to do it relatively easily with little or no user  
config.

/Janne

On 5 Feb 2008, at 18:49, Terry Steichen wrote:

> Janne,
>
> What would that do to those of us using the JDBCPageProvider (and the
> thousands of pages implemented via that WikiPageProvider)?
>
> Terry
>
> PS: Sorry, but I'm also beginning to wonder if these grand and  
> glorious
> plans aren't taking JSPWiki in a direction that will drastically alter
> the characteristics that attracted me to it from the outset.
>
>
> On Tue, 2008-02-05 at 18:12 +0200, Janne Jalkanen wrote:
>
>>> So you don't see any way of using a JSPWiki 3.0 implementation
>>> *without* JSR-170?
>>
>> Exactly.  It would be duplication of work.  And mostly really stupid
>> work, too, since it would mean reinventing the JSR-170 concepts.
>>
>>> I'm rather surprised, really. One of the real
>>> strengths of JSPWiki is that there's a nice, lightweight file
>>> system implementation too.
>>
>> The job of the lightweight file system implementation is the job of
>> the backend, in this case, JSR-170.  It makes a lot of sense to
>> separate backend (i.e. storage) under a separate API, and where we
>> now use the WikiPageProvider, we can get far better support by using
>> JCR.
>>
>>> If the entry ramp is a complex database
>>
>> Nobody said anything about complex databases.
>>
>> I have, over the past year, been writing a lightweight implementation
>> of JSR-170, which uses a very similar pluggable provider system like
>> the current WikiPageProvider.  And yes, it ships with a lightweight
>> file system provider as well.  And no, it does not pass the TCK yet.
>> And yes, I was planning to offer it as the default JCR Repository for
>> JSPWiki 3, and yes, users who need HA or scalability can then switch
>> to Jackrabbit at the flick of a switch.
>>
>> Murray, calm down.  I wouldn't want to throw away the advantages of
>> JSPWiki, and I also still do not particularly like databases.
>>
>> /Janne