forrest-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ross Gardler (JIRA)" <>
Subject [jira] Created: (FOR-948) Refactor the creation of the pipeline output document
Date Mon, 04 Dec 2006 01:55:20 GMT
Refactor the creation of the pipeline output document

                 Key: FOR-948
             Project: Forrest
          Issue Type: Improvement
          Components: Forrest2
            Reporter: Ross Gardler
            Priority: Minor

The org.apache.forrest.core.Controller has a rather hacky implementation of the ".forrestPipeline"
url extension. This extension provides an XML representation of the pipeline that is generated
to process a specific request.

The implementation is really horrible, the document is created as a stiring, it requires a
number of fields to capture pipeline details (such as readerClass, inputPluginClass and outputPluginClass).
These variables are written in the various stages of pipeline processing.

It would be better if we had a specialist PipelineDescriptionOutputDocument class that contains
all the relevant information abut the pipeline. This could be manipulated during pipeline
processing. For example:

public class PipelineDescriptorClass() extends DefaultOutputDocument {

  public void addReader(Reader reader) {...}

  public void addInputPlugin(IPlugin plugin) {...}

  public void addOutputPlugin(IPlugin plugin) {...}



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