DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=43813>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=43813 ------- Additional Comments From [EMAIL PROTECTED] 2007-11-08 12:09 ------- (In reply to comment #2) > The problem is that a module can contain more than one resource type. For > instance the forrest module will contain resource types for "normal", FAQ, > changes, ... documents. but is that worth it? wouldn't it simplify things a lot if we mandate one doctype == one module? afaik multiple doctypes per module are not widely used, and splitting them would be trivial. then we could get rid of some code and replace another layer of configuration with convention. the fallback resolver hack is really frightful, and totally unnecessary imho given that we could just as well handle the stuff in sitemaps, where all the glorious resolvers are available without limitations and hacks. wdot? that said, i'd also like to re-discuss the formats post 2.0. do we really need formats as a configurable with a corresponding input module, or could we just use matchers in the resource type module sitemaps and define these as an API? reduces overhead, gets rid of indirection, makes stuff more self-explanatory. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
