The following comment has been added to this issue:
Author: David Sean Taylor
Created: Fri, 28 May 2004 11:52 AM
Body:
> 1. support for multiple pipelines
> You would register multiple pipelines as indvidual components within the root
> container.
There are currently 2 pipelines in J2.
We need to continue support of these 2 pipelines (and potentially more)
> 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.
The JetspeedEngine currently does this. Sounds like an easy conversion
> 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.
Cool. just making sure.
I
> 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 >kewl!
It does sound cool. Im fine with it.
+1
---------------------------------------------------------------------
View this comment:
http://issues.apache.org/jira/browse/JS2-61?page=comments#action_35781
---------------------------------------------------------------------
View the issue:
http://issues.apache.org/jira/browse/JS2-61
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
Components:
Other
Versions:
2.0-a1
Assignee: Scott T Weaver
Reporter: Scott T Weaver
Created: Fri, 28 May 2004 8:14 AM
Updated: Fri, 28 May 2004 11:52 AM
Description:
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.
---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
