Believe it or not, but the JSPwiki code is already ported on components - OSGi of a bandles, and...: - the layer of visualization has produced with use of Eclipse RAP; - data are submitted by EMF model; - the persistence of data is carried out by means of CDO.
Screenshot of the functioning wiki - see https://yadi.sk/i/UezpmVo63Tf4 2g (in the picture: at the left - IDE; on the right - the browser with ElWiki). There is a one change in syntax of a wiki-marking - for references between pages it is required to specify the page identifier. For example: [Sample page | @218] Because of it the name wiki is: ElWiki (Enhanced links wiki). The data model of these pages is organized hierarchically, references between them are based on identifiers of pages. So existence of pages with identical names, for example in different branches of wiki is possible. Used data model is presented here - https://yadi.sk/i/jaljk1m23Tf3zw In the presented realization there is no need to load all pages, for processing of communications between them. Work on the project is continued. (changes has been started and continuing by me) PS: In general, I use JSPwiki for logging of my practices, notes from books, articles. Though in my option - the pages of JSPwiki are stored in the database, not on a disk, but in general, loading all pages in memory, impossibility to set the any name of page, and etc. -- doesn't suit me now. On Чт, 2018-03-22 at 08:26 +0100, Jürgen Weber wrote: > guess not, on startup JSPWiki loads all pages into memory to parse > intra-page links. > > 2018-03-22 5:24 GMT+01:00 dagarwa...@gmail.com <dagarwa...@gmail.com> > : > > > > JspWiki uses filesystem instead of a conventional database. Would > > you suggest using jspwiki if it were to cater to 1billion page ? > > (Provided, a solid backup mechanism ). Would it scale that much > > with both performance and data-integrity perspective ?
