|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
02/Apr/05 01:37 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.
|
|
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. |
Show » |
made changes - 02/Apr/05 01:37 AM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
Closed
[ 6
]
|
|
Resolution
|
|
Won't Fix
[ 2
]
|
|
Task
Closed
Major
Move pipeline assembly out of XML and into jetspeed.groovy assembly
