forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [JIRA] Commented: (FOR-439) Allow plugins to register new cocoon components
Date Fri, 18 Feb 2005 13:03:32 GMT
The following comment has been added to this issue:

     Author: Ross Gardler
    Created: Fri, 18 Feb 2005 7:02 AM
The problem with this solution is that it breaks the copyless behaviour.

I have a partial implementation on my hard drive that uses the new ability in cocoon to include
xconf files, but does not break copyless. However, I've stalled on its development at present
because some components also need to add info to web.xml and I have not figured out a way
of doing this in a copyless environment and I don't have time to finish it off right now.

If you are able to help complete this work I will create a branch for us to work in.
View this comment:

View the issue:

Here is an overview of the issue:
        Key: FOR-439
    Summary: Allow plugins to register new cocoon components
       Type: Improvement

     Status: Unassigned
   Priority: Minor

    Project: Forrest
             Plugins (general issues)

   Reporter: Bastian Bowe

    Created: Fri, 18 Feb 2005 6:35 AM
    Updated: Fri, 18 Feb 2005 7:02 AM

Plugins are not able to add new components or parts to the xconf. A concrete use case could
be to add

      logger="core.modules.mapper" name="foo"/>

to <input-modules/>

A possible implementation could copy <FORREST_HOME>/main/webapp/WEB-INF/xconf/forrest-core.xconf
to <project.dir>/build/tmp and apply for all plugins ${plugin.dir}/internal.xconf or
something using ant's the xpatch task. My given
idea might be invalid as I've never used xpatch but something similar should be possible.

At least it should be possible to copy the xconf to a temporary location and let the plugin's
build.xml use xpatch by itself to allow arbitary customizations. Please keep in mind that
"forrest webapp" still has to be functional.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message