I found an interesting and (to me) unexpected effect when doing this. The request to the cocoon protocol is the request as you've processed it thus far, so you can use the request to modify the result of the cincluded pipeline as you need.
What do you mean with that? The cocoon:// requests will use the same Request object and Session than the main
pipeline, won't them?
Yes they do. All I was saying was I didn't expect that; I had guessed (wrongly) that the cincluded content would be independent from the request cincluding it. The cocoon behavior is perfectly logical and desired. I'm using cocoon for my first server side development so maybe this is obvious behavior to everyone else; it was unexpected at that point in my learning.
Steve
_________________________________________________________________
Set yourself up for fun at home! Get tips on home entertainment equipment, video game reviews, and more here. http://special.msn.com/home/homeent.armx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
