DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10281>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10281 PATCH: nested cocoon: source spanning multiple sitemaps Summary: PATCH: nested cocoon: source spanning multiple sitemaps Product: Cocoon 2 Version: Current CVS Platform: All OS/Version: All Status: NEW Severity: Normal Priority: Other Component: core AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] in a sitemap: <match pattern="match"> <generate src="cocoon:/subsitemap/match"/> <serialize/> </match> <match pattern="subsitemap/**"> <mount uri-prefix="subsitemap" src="subsitemap/" check-reload="yes"/> </match> in a subsitemap: <match pattern="match"> <generate src="cocoon:/johnny"/> <serialize/> </match> <match pattern="johnny"> <generate src="johnny.xml"/> <serialize/> </match> This is obviously a contrived example... but it looks like it should work. If you view "subsitemap/match", it will work. If you view "match" you will get an error saying that no pipeline matched "johnny" because it will look for johnny in the first sitemap rather than the subsitemap. This patch gives the pipeline knowledge of which processor it belongs to when the generator is set, then reminds it which processor to use when the pipeline is setup. This corrects the problem. I've only tested with the treeprocessor, but i assume that if the compiled sitemap had the bug, this fix will pertain to it as well. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
