cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lars Trieloff (JIRA)" <>
Subject [jira] Updated: (COCOON-1899) [PATCH] Cocoon XML:DB Implementation should not depend on Xindice
Date Sat, 26 Aug 2006 20:15:23 GMT
     [ ]

Lars Trieloff updated COCOON-1899:

    Attachment: cocoon-xindice-as-own-block-rev437218.patch

The patch 
- removes xindice from the list of dependencies in cocoon-xmldb-impl
- creates a new block cocoon-xmldb-xindice
- moves xindice-specific configurations from cocoon-xmldb-impl to cocoon-xmldb-xindice
- adds a dependency to cocoon-xmldb-xindice to cocoon-xmldb-sample

> [PATCH] Cocoon XML:DB Implementation should not depend on Xindice
> -----------------------------------------------------------------
>                 Key: COCOON-1899
>                 URL:
>             Project: Cocoon
>          Issue Type: Improvement
>          Components: Blocks: XML-DB
>    Affects Versions: 2.2-dev (Current SVN)
>            Reporter: Lars Trieloff
>            Priority: Minor
>         Attachments: cocoon-xindice-as-own-block-rev437218.patch
> Currently the cocoon-xmldb-impl block depends on Xindice as an XML database. This leads
to a number of problems when the user decides to use a different XML database, e.g. Exist:
> - the configuration files injected by the build system still refer to Xindice
> - Xindice is deployed as a JAR file in the application, regardless of not being in use
by the application
> - It is not easy to add a different XML database by adding a new cocoon block that contains
cocoon-specific configuration files.
> A better configuration would be the removal of all references to Xindice in cocoon-xmldb-impl
(dependencies as well as configuration files) and the creation of a new block cocoon-xmldb-xindice
that depends on Xindice and brings all configuration files neccessary to use Cocoon with Xindice.
Accordingly cocoon-xmldb-examples should depend on cocoon-xmldb-xindice as well.
> This configuration makes it easy to create a new block for other XML-databases, e.g.
Exist. Switching to a new XML-database would be as easy as changing the dependency in the
pom and updating all connection-uris in the sitemap.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:


View raw message