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, 04 Jun 2004 12:46:53 GMT
The following comment has been added to this issue:

     Author: Scott T Weaver
    Created: Fri, 4 Jun 2004 5:45 AM
RequestContexnt extending Map would still require all the dependencies that RequestContext
requires.  So I am -1 one on that just because it keeps the pipeline to tightly bound to the
jetspeed/portal/pluto apis.

I also feel that Object is to generic.

Maybe an array of Objects, like an arg list instead of a map.

Unfortunatley I have no good suggestions right now what we should be passing around within

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, 4 Jun 2004 5:45 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