Joerg Heinicke schrieb: > > Both possible pipeline "paths" would be correct. Only problem is to find > the mutually exclusive patterns as you run into the second match > otherwise and have 2 generators. And I think here is where Rainer had > his problems, there is no "not" to just inverse the first condition with > the wildcard matcher (while the selector just has an otherwise). Rainer > might confirm my understanding :-)
That is it exactly. Most suggestions depend in the end on having mutually exclusive patterns. > >> Solprovider suggested to use resources but I would go with several >> different internal pipelines that >> would work as generators. > > Resources are indeed a kind of work around. You don't need mutually > exclusive patterns anymore since inside each matcher you have a complete > pipeline. > > I prefer your internal pipelines approach though since it is much more > flexible and closer to the original idea. It also has advantages in > terms of caching since internal pipelines are cached separately. > > Joerg I also prefer using pipelines over resources. With 2.1.x I made heavy use of resources but this quickly turns out quite complex, if you enter using cascaded resources and passing along numerous parameters. However, I am a bit reluctant adding another level of pipelines just for implementing a 2-n valued alternative. This quickly turns out (unnecessarily) complex either. As I am not aware of a simple component providing such functionality on urls, I asked here. Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
