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=23969>. 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=23969 NPE in redirect-to Summary: NPE in redirect-to Product: Cocoon 2 Version: 2.1.2 Platform: PC OS/Version: Windows NT/2K Status: NEW Severity: Normal Priority: Other Component: sitemap components AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] this simple pipeline causes an NPE: <map:match pattern="xsl/test"> <map:generate src="cocoon:/test"/> <map:serialize/> </map:match> <map:match pattern="test"> <map:redirect-to uri="foo"/> </map:match> before saying "you can't redirect after a generator is called", consider: calling another pipeline with the cocoon: protocol is the only way to have one main pipeline (which does authentication, i18n, etc) which calls out to subsitemaps for page-specific behavior*. each page may decide to redirect before any "real" generator is called (aka no sax events yet). this is an important organizational technique for any large site. so if not a bug, please consider it an important feature. i'm going to try a workaround which uses xhtml and xslt to create an html response which has a meta-refresh tag. *ack* the problem with this approach is that the main pipeline still gets executed and our banner html is applied along with i18n, etc, just to redirect :( * resources don't work in this case because our subsitemap needs to invoke pipeline fragments in the root sitemap. root-level resources aren't visible from a subsitemap, so we must use the cocoon: protocol everywhere.
