[Mono-bugs] [Bug 70841][Nor] New - weird namespace handling bug around XslTransform.AddExtensionObject
bugzilla-daemon@bugzilla.ximian.com
bugzilla-daemon@bugzilla.ximian.com
Tue, 28 Dec 2004 06:41:06 -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 atsushi@ximian.com.
http://bugzilla.ximian.com/show_bug.cgi?id=70841
--- shadow/70841 2004-12-28 06:41:06.000000000 -0500
+++ shadow/70841.tmp.3948 2004-12-28 06:41:06.000000000 -0500
@@ -0,0 +1,72 @@
+Bug#: 70841
+Product: Mono: Class Libraries
+Version: 1.0
+OS:
+OS Details:
+Status: NEW
+Resolution:
+Severity:
+Priority: Normal
+Component: Sys.XML
+AssignedTo: atsushi@ximian.com
+ReportedBy: atsushi@ximian.com
+QAContact: mono-bugs@ximian.com
+TargetMilestone: ---
+URL:
+Cc:
+Summary: weird namespace handling bug around XslTransform.AddExtensionObject
+
+running monodoc's EcmaHelpSource.Htmlize() under MS.NET results in an
+exception with related to handling extension object, while Mono does not
+(not sure if it is mono bug right now).
+
+Actual Results:
+
+No error.
+
+Expected Results:
+
+System.Xml.Xsl.XsltException: Function 'monodoc:MonoEditing()' has failed.
+---> System.MethodAccessException: Attempt to access the method failed.
+ at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj,
+BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
+culture, Boolean isBinderDefault, Assembly caller, Boolean verifyAccess)
+ at System.Reflection.RuntimeMethodInfo.InternalInvoke(Object obj,
+BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo
+culture, Boolean verifyAccess)
+ at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags
+invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
+ at System.Reflection.MethodInfo.Invoke(Object obj, Object[] parameters)
+ at System.Xml.Xsl.FuncExtension.Invoke(XsltContext xsltContext, Object[]
+args, XPathNavigator docContext)
+ at System.Xml.XPath.XsltFunction.InvokeFunction(XPathNavigator qy,
+XPathNodeIterator iterator)
+ --- End of inner exception stack trace ---
+ at System.Xml.XPath.XsltFunction.InvokeFunction(XPathNavigator qy,
+XPathNodeIterator iterator)
+ at System.Xml.XPath.XsltFunction.getValue(XPathNavigator qy,
+XPathNodeIterator iterator)
+ at System.Xml.XPath.BooleanFunctions.toBoolean(XPathNavigator qyContext,
+XPathNodeIterator iterator)
+ at System.Xml.XPath.BooleanFunctions.getValue(XPathNavigator qy,
+XPathNodeIterator iterator)
+ at System.Xml.XPath.XPathNavigator.Evaluate(XPathExpression expr,
+XPathNodeIterator context)
+ at System.Xml.Xsl.Processor.EvaluateBoolean(ActionFrame context, Int32 key)
+ at System.Xml.Xsl.IfAction.Execute(Processor processor, ActionFrame frame)
+ at System.Xml.Xsl.ActionFrame.Execute(Processor processor)
+ at System.Xml.Xsl.Processor.Execute()
+ at System.Xml.Xsl.XslTransform.Transform(IXPathNavigable input,
+XsltArgumentList args, TextWriter output, XmlResolver resolver)
+ at Monodoc.EcmaHelpSource.Htmlize(IXPathNavigable ecma_xml,
+XsltArgumentList args)
+ at Monodoc.EcmaHelpSource.RenderNamespaceLookup(String nsurl, Node&
+match_node)
+ at Monodoc.RootTree.RenderUrl(String url, Node& match_node)
+
+
+How often does this happen?
+consistently.
+
+Additional Information:
+The repro I get is from paco, not available right now.