> I think that we should add a
> getVariable(QName) method to ExpressionContext so that extensions can
rely on
> getting the variable directly from the ExpressionContext rather than
having to
> figure out how to cast it or go through other gyrations.
OK by me.
-scott
bugzilla@apac
he.org To: [EMAIL PROTECTED]
cc: (bcc: Scott Boag/CAM/Lotus)
07/04/2001 Subject: [Bug 2355] - VariableStack
access by QName
01:48 PM
Please
respond to
xalan-dev
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=2355
*** shadow/2355 Wed Jul 4 03:26:47 2001
--- shadow/2355.tmp.23448 Wed Jul 4 10:48:43 2001
***************
*** 43,45 ****
--- 43,68 ----
I'm open to suggestions, especially if there are less fragile mechanisms
for
getting an XPathContext from an ExpressionContext.
+
+
+ ------- Additional Comments From [EMAIL PROTECTED] 2001-07-04 10:48
-------
+ Scott --
+
+ This seems like a reasonable thing to want to do. I think that we should
add a
+ getVariable(QName) method to ExpressionContext so that extensions can
rely on
+ getting the variable directly from the ExpressionContext rather than
having to
+ figure out how to cast it or go through other gyrations.
+
+ One of the benefits of the DTM work, I think, is that the cast of
+ ExpressionContext to XPathContext, which used to work, was a shortcut
that hid
+ the visibility of what sorts of things extensions were trying to do. So,
+ "breaking" the cast with the DTM work will allow us to become aware of
these
+ issues and include them, as appropriate, in the ExpresionContext
interface. A
+ long-term benefit for some short-term pain.
+
+ If there are no objections, I'd like to add getVariable(QName) into
+ ExpressionContext and into its implementors.
+
+ Thoughts?
+
+ Gary
