Fair enough. OK, so Struts can loop through all UnknownHandlers it finds declared in various .xml files. Since there is no central configuration when working with plugins, how can sequence/prioritize how each set of rules gets evaluated? Without something like a routes.rb, things can get confusing in a hurry as plugins bring that kind of configuration with them. Perhaps put a plugin-stack setting, similar to the interceptor-stack, in struts.xml?
Musachy Barroso wrote: > >> Don's point is a valid one, but I also hope that he agrees that its a >> good >> thing to somehow combine REST and Convention. I am not so sure that >> changing how Struts fundamentally works so that we can include more and >> competing plugins at runtime is a good thing. It is that type of >> confusion >> that makes the framework hard for the masses to absorb. >> > > I agree if you are talking in general, but in this case I think it is > an improvement if anything. If you add 2 plugins that handle different > url patterns and they both define UnknownHandler(s), even when at > runtime they should co-exist peacefully, you will get an exception > when the xmls are loaded. I think this is a bug in the framework, and > we are seeing its effects on the Codbehind vs Convention collision > problem. > > musachy > > -- > "Hey you! Would you help me to carry the stone?" Pink Floyd > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/-VOTE--Bring-Convention-plugin-into-trunk-and-deprecate-Zero-Config-tp17222798p17603378.html Sent from the Struts - Dev mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
