But, I want to make sure that people understand -- this is code under rapid development; there are no API guarantees; and it may be a while before it's well documented. The source is wide open, and the lists are available for questions and criticisms -- but if you just want to use it and don't want to understand how it works, then you should probably wait for a regular release.
It is really helpful to have people start building applications around the code -- nothing else provides the kind of testing necessary to really flush out issues -- but people who do this should be ready for periodic tweaking to respond to API changes and such until there's a full release.
Joe
At 9:45 AM +0000 2/9/05, Niall Pemberton wrote:
In Struts 1.2 you can configure different RequestProcessors for different modules, but you can' t have different RequestProcessors for the same module. Struts 1.3 (under development) is based on the Chain of Responsibilty (CoR) pattern (using Jakarta Commons Chain) - that introduces alot more flexibility in how you can configure "request processing". Sounds like it might be worth you downloading the "nightly" build and having a look at that.
Niall
----- Original Message ----- From: "Sandip Khetle" <[EMAIL PROTECTED]> Sent: Wednesday, February 09, 2005 9:25 AM
hi
Thank You very much for ur help Niall....I have one more question ......
Can we have multiple RequestProcessor classes for a single application .....I mean as we have a single ActionServlet is it mandatory to have a single RequestProcessor as well...?
thanks in advance...
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--
Joe Germuska [EMAIL PROTECTED] http://blog.germuska.com "Narrow minds are weapons made for mass destruction" -The Ex
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
