portals-jetspeed-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Commented: (JS2-61) Move pipeline assembly out of XML and into jetspeed.groovy assembly
Date Fri, 28 May 2004 18:34:01 GMT
The following comment has been added to this issue:

     Author: Scott T Weaver
    Created: Fri, 28 May 2004 11:33 AM
> 1. support for multiple pipelines
You would register multiple pipelines as indvidual components within the root container.

> 2. ability to select your pipeline in the http request -- no change 
> to that functionality.
Reference the pipeline by the ket it is registered under in the root container.

> 3. ability to have logic in pipeline, and have simple workflow caps 
> such as have a valve short-circuit the process as the ActionValve 
> does
I am not proposing changing the currently funtionallity of the pipeline/valves at all.  The
actual classes would not change at all except for removing the need for Descriptor objects.

> 4. continue the valve concept
See number 3

> 5. Keep the pipeline concept. This is my concept and contribution to
> J2. I feel its a core piece of the Jetspeed architecture, and don't 
> want to throw aside in the zealous pursuit of COP.

Nowehere in my proposal did I ever mention removing the current pipeline/valve approach. 
It is the core of the way J2 works and I personally think is one of the things that makes
J2 such an extensible piece of software.  I just want to make configuring/assembling Jetspeed
as much of a "one stop shopping experience" as possible.

By using Pico to assemble the pipeline, we can capitalize on all the pico has to offer. I
think the ability to hotswap a valve or even an entire pipeline, real-time is pretty damn

View this comment:

View the issue:

Here is an overview of the issue:
        Key: JS2-61
    Summary: Move pipeline assembly out of XML and into jetspeed.groovy assembly
       Type: Task

     Status: Open
   Priority: Major

    Project: Jetspeed 2

   Assignee: Scott T Weaver
   Reporter: Scott T Weaver

    Created: Fri, 28 May 2004 8:14 AM
    Updated: Fri, 28 May 2004 11:33 AM

Having the pipeline's valve assembly defined within an XML smells funny as it is describing
"guts" (i.e. class names) with in a configuration script instead of assembly.  Moving this
into jetspeed.groovy AND making  the JetpseedPipline extend pico container and deploy it as
a sub-container makes a whole lotta sense to me.

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:

To unsubscribe, e-mail: jetspeed-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-dev-help@jakarta.apache.org

View raw message