Re: composable RequestProcessor

[Matthias Bauer]

If the list of extension grows (Tiles, Worklfow Extension, Expresso, 
...) the number grows exponentially. You need to implement a  class 
for each possible combination of extensions:

1. your extension alone
2. your extension + tiles
3. your extension + workflow
4. your extension + tiles + workflow
5. your extension + expresso
6. your extension + expresso + tiles
7. your extension + expresso + workflow
8. your extension + expresso + tiles + workflow


You need to make a decision in your app about what technologies you 
will use.  When you add a technology you will modify the processor 
accordingly.  You don't need a class for every combination, just one 
for the combination being used in your app.

I don't doubt that you would be able to compose a request processor from 
the various processors that come with the different extensions. But the 
normal struts user will not be able to do that. He will not know what to 
do to bring Struts Workflow together with Tiles, believe me.

--- Matthias





---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]