>
> Yes, JSR-170 (despite some comments that I have heard about
performance) is roadmapped for JSPWiki 3.0 to replace the entire back
end. In case you have not noticed, we're already past 2.0, we're at
2.4... ;-)
>
I must be lagging!
> However, we'll probably need to use by default something else than
Jackrabbit, since it does not have a proper SPI.
>
I think it is pluggable.
>
> JSR-170 is not that complicated if you don't need the entire
implementation. All we need is the core functionality + versioning;
everything else we already have within JSPWiki as such, or can be
provided by other libraries.
hmmm, I was thinking of going all the way!
Besides versioning it offers accesscontrol, queries (xpath/sql), search,
locking, import/export (a very big wish). It supports multiple
persistence managers (filesystem/db/oodb etc.).
Also tools will evolve around jsr 170. (There's an interesting sync
appliation being build). Imagine diff/merge tools etc.
JSPWiki can then concentrate on the wiki itself instead of all the
plumbing around it. Maybe all wiki's together can think about an
universal wiki-content specification (just dreaming, i know).
Just my 2cents.
Kees Kuip
_______________________________________________
Jspwiki-users mailing list
[email protected]
http://ecyrd.com/cgi-bin/mailman/listinfo/jspwiki-users
