You put things into the pipeline by creating an entry in a pipeline.xml
file. See WEB-INF/conf/turbine-classic-pipeline.xml
There are a number of valve classes in the org.apache.turbine.pipeline
package.
It is very straight forward. I have worked on this myself so let me know
if I can help.
Regards,
Peter
Jürgen Hoffmann wrote:
Hi Thomas,
Since I have not yet looked at the pipeline, and just read on the Website
about it, how do we handle this? Do I send you the classes off list, or ist
it best to create a patch on the existing t2.4 code, since i wanted to look
into the code later this week anyways?
If we put this onto the pipeline, can this be configurable? I.e. can I
configure what goes into the pipeline via TR.props?
I guess everything clears out, when I have looked at the code.
Am Sonntag, 25. Juni 2006 21:23 schrieb Thomas Vandahl:
Jürgen Hoffmann wrote:
[stuff deleted]
Does that sound like a reasonable solution?
Absolutely. This seems to fit perfectly into the Turbine pipeline
concept. I would like to have a look at it.
Bye, Thomas.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!EXCUBATOR:1,449ee2e377969174928051!
--
------------------------------
Peter Courcoux
Telephone : +44 (0)1923 661488
Mobile : 07880 605626
email : [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
