[Mono-bugs] [Bug 70841][Nor] Changed - mono-ecma.xsl transformation results in XsltException under MS.NET (CAS matter)

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Thu, 30 Dec 2004 15:00:21 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by sebastien@ximian.com.


--- shadow/70841	2004-12-30 14:45:00.000000000 -0500
+++ shadow/70841.tmp.4681	2004-12-30 15:00:21.000000000 -0500
@@ -82,6 +82,22 @@
 ------- Additional Comments From atsushi@ximian.com  2004-12-30 14:45 -------
 The method invoked via extension object in XsltArgumentList
 (ExtensionObject class in monodoc/browser/ecma-provider.cs) is not
 publicly accessible, and the stack trace from MS.NET looks exactly
 indicating that.
+------- Additional Comments From sebastien@ximian.com  2004-12-30 15:00 -------
+I don't think it's "CAS" related (unless the assembly is executed from
+a network, i.e. not FullTrust - and that would show somewhere else
+with SecurityException) but I still think it's security related.
+My guess is that the Transform method is called without a XmlResolver,
+which means that (for fully trusted code) a default XmlUrlResolver is
+being used. The XmlUrlResolver class only accept file:// and http://
+protocols and (maybe) choke on the monodoc:// custom protocol.
+args.AddExtensionObject("monodoc://extensions", ExtObject);
+and the exception is thrown later because something (the monodoc
+object) is missing.