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=43853>. 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=43853 Summary: rng include resolving does not work with proxy Product: Lenya Version: Trunk Platform: Other OS/Version: other Status: NEW Severity: blocker Priority: P2 Component: Bitflux Integration AssignedTo: [email protected] ReportedBy: [EMAIL PROTECTED] client-side rng validation (as used by bxe) currently fails in proxied environments, because the include hrefs are not correctly resolved. we have a strange re-implementation of a fallback resolver in src/webapp/lenya/xslt/resources/translate-rng-includes.xsl that just knows contexts, not proxies. it really needs to go away rsn. for now, i'm removing the context prefix and apply a proxy transform later on (which means the proxy transformer has to be re-configured to include rng:includes...) we should really be more careful with using cocoon-internal protocols in files that will potentially be parsed on clients (currently, these are rngs and xslt - mozEdit anyone?). imnsho, they should not be served from files at all but via the module sitemaps, with proper proxy transforms applied. -- 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]
