You are viewing a plain text version of this content. The canonical link for it is here.

Posted to docs@cocoon.apache.org by do...@cocoon.apache.org on 2004/07/09 13:14:05 UTC

[Cocoon Wiki] Updated: EXistAsBlock

   Date: 2004-07-09T04:14:05
   Editor: DerekLastname <dh...@csir.co.za>
   Wiki: Cocoon Wiki
   Page: EXistAsBlock
   URL: http://wiki.apache.org/cocoon/EXistAsBlock

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -1,5 +1,5 @@
 '''Building eXist as a Cocoon2.1 Block'''
-With its support for the XQuery language and snappy performance, the [http://exist.sf.net eXist] XML:DB database server is quite attractive to existing Cocoon projects considering the advantages of a database backend. Indeed eXist is distributed as a Cocoon project, and instructions are EXistInCocoon on this wiki explaining how to add eXist to a project that is already in full flight.
+With its support for the XQuery language and snappy performance, the [http://exist.sf.net eXist] XML:DB database server is quite attractive to existing Cocoon projects considering the advantages of a database backend. Indeed eXist is distributed as a Cocoon project, and instructions are [:EXistInCocoon] on this wiki explaining how to add eXist to a project that is already in full flight.
 
 To my mind, though, both of these approaches force the developer to mingle two projects in just the sort of way that Cocoon's block architecture hoped to help avoid. In Cocoon2.1.4 Xindice, after all, has its own block that provides the XMLDB service and illustrates its use. Why shouldn't eXist?