xwiki

Xwiki is a J2EE Wiki - clean architecture and implemented using many common APIs/Layers. i set this up, tested around, talked to the author. Xwiki is designed as a enterprise level wiki with some generic capabilities. e.g. inheritance model in the background, xwiki pages (or templates) can be modeled with fields/attributes (different gui types available). With this page creation can be forced to be done via forms, a new page is then a specific object of the original template class (even multiple inheritance is supported); attributevalues of that page are stored in a relational way (behind hibernate). structured storage of wiki content is possible with this (if you set it up appropriate). personally verified Xwiki Capabilities are:
Radeox Wiki Engine Syntax; view,edit,preview,save,version control (xwiki page history), attachments,full text search,rights management,enterprise persistence Layer hibernate (allows mysql or oracle, db2 behind); design engine for documents,forms,metadata; presentation layer: velocity. allows velocity coding in pages - this allows access on the internal classmodel!;inline editing ! a xwiki page is a object (with attributes) of an given class (templates), inline editing switches to an editing mode and those parts of text which are attribute values are now presented inline als form input fields (different types), this can be based upon special rights; RSS output an inline external RSS Feed presentation; multilanguage capabilities;interal use of opensymphony j2ee components

i did not looked at the following features:
integrated stats, portlet integration, xml/rpc access, pdf export, wysiwyg html editing, skin system