forrest-dev mailing list archives

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

     Author: Bastian Bowe
    Created: Fri, 18 Feb 2005 7:26 AM
       Body:
Allright I would like to give it a try.
---------------------------------------------------------------------
View this comment:
  http://issues.cocoondev.org//browse/FOR-439?page=comments#action_12046

---------------------------------------------------------------------
View the issue:
  http://issues.cocoondev.org//browse/FOR-439

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
 Components: 
             Plugins (general issues)

   Assignee: 
   Reporter: Bastian Bowe

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

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

<component-instance
class="foo.cocoon.components.modules.input.SpecialLinkModule"
      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. http://wiki.apache.org/cocoon/XPatchTaskUsage. 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.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.cocoondev.org//secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message