Great! That was fast.
Gary
[EMAIL PROTECTED] wrote:
>
> I believe I have a fix for this. I had to change a few things so I'll run
> it by Scott before I check in.
>
> Myriam
>
>
> Myriam_Midy@lo
> tus.com To: [EMAIL PROTECTED]
>
I believe I have a fix for this. I had to change a few things so I'll run
it by Scott before I check in.
Myriam
Myriam_Midy@lo
Yes. That is what I was looking into as well but there are a number of
callers. Actually, I was thinking of passing in an XPathContext because
that seems to be available when needed. There are some cases where an
empty NodeSetDTM is created and never populated so those don't really
need an XPat
No, that's what I'm thinking too. I was thinking of passing in a DTMManager
when we create a NodeSetDTM. The question is, when we create these things,
do we always have one available?
I'll look into it some more.
Thanks,
Myriam
Myriam --
I entered this as bugzilla 2642. The problem is that
org.apache.xpath.NodeSetDTM returns null for getDTM(). Is this what
you're talking about? If so, please go ahead and fix it since I was
still trying to figure out where to get the DTMManager into NodeSetDTM.
If you're thinking abo
Gary, are you looking at fixing this bug? I think I know what needs to be
done, but I don't want to do anymore if you're already working on it.
Thanks,
Myriam
Gary L Peskin
Daniel Einspanjer wrote:
>
> I appreciate the pointer. Starting from http://xml.apache.org, I don't see anything
>that points to 2.1.0. I just grabbed it and I'll try it out.
Don --
We currently only point to the latest release. I think we should have
both the latest production release as w
Daniel --
Get the latest production release 2.1.0 at
http://xml.apache.org/dist/xalan-j/
I have verified that this is a problem in the developer release 2.2.D6
and I've entered it into bugzilla as bug 2642.
Thanks,
Gary
Daniel Einspanjer wrote:
>
> Well I have great news to begin with, IT WOR
Well I have great news to begin with, IT WORKS! On your advice, I went back to
xml.apache.org and downloaded the xalan-j2_2_D6. I downloaded 1.2.2 because I thought
it was the latest release version, but if the development version works for what I
need, I'll go with it.
Unfortunately, I am n
Sorry about the "G" in ApplyXPathG. Just my fat fingers. It should be
ApplyXPath.
Gary
Gary L Peskin wrote:
>
> Oh, I forgot to mention, that I also tried:
>
> java ApplyXPathG new.xml "id('a')"
>
> and got the following results:
>
> Loading classes, parsing Daniel\new.xml, and setting u
Oh, I forgot to mention, that I also tried:
java ApplyXPathG new.xml "id('a')"
and got the following results:
Loading classes, parsing Daniel\new.xml, and setting up serializer
Querying DOM using id('a')
Gary
Gary L Peskin wrote:
>
> Daniel --
>
> This worked for me just as is. Here
Daniel --
This worked for me just as is. Here are my results:
C:\Temp\Daniel>java IDTest
Has Child Nodes: true
Name: test
Value: null
Is this what you got or do you get some kind of exception? This looks
like it's working fine on my system.
The version of XalanJ that you're using is
Thank you very much for taking a look at this! Attached is a zip with a very simple
test case.
If you would be able to get this to work, I could easily apply it to my work since I
am basically
doing the same thing.
-- Daniel Einspanjer, [EMAIL PROTECTED] on 07/13/2001
On Fri, 13 Jul 2001 12:0
>I found the DOM spec you referred to. I guess now I am trying to find out
what DOM >implementation does support id().
I believe the Xerces DOM does, but _ONLY_ for nodes built by the validating
parser. If you don't validate, or if you created the node explicitly via
the DOM interface, I think
Daniel --
Did you ever get this working? If not, please attach your XML document
and the XPath expression that you're using. If you're building the DOM
from other than a text file, change your application to write out the
serialized DOM by including
FileOutputStream fos = new FileOutputStream
This is very useful information, and I thank you for it.
I found the DOM spec you referred to. I guess now I am trying to find out what DOM
implementation does support id().
I tried using the org.apache.xerces.parsers.DOMParser's getDocument() method which
uses the org.w3c.dom, but a call
to t
If you're using a DOM as input, support for the id() function is dependent
upon the DOM's getElementByID() function. So the real question here is why
your DOM isn't providing that information.
Quoting the DOM spec:
Note: The DOM implementation must have information that says which
attribute
On Thu, 12 Jul 2001 01:15:09 +0200 (CEST), Erwin Bolwidt wrote:
>On Wed, 11 Jul 2001, Daniel Einspanjer wrote:
>
>> I have been struggling with trying to get the XPath id() function to
>> work in the application I am writting. I have a DTD that defines an ID
>> attribute and an xslt that performs
On Wed, 11 Jul 2001, Daniel Einspanjer wrote:
> I have been struggling with trying to get the XPath id() function to
> work in the application I am writting. I have a DTD that defines an ID
> attribute and an xslt that performs some custom html translation.
> During runtime, I load the xml docum
I am very sorry for posting this to a development group, but I could not find an
xalan-users group, and I have not gotten any responses from xerces-j-users. :/
I have been struggling with trying to get the XPath id() function to work in the
application I am writting. I have a DTD that defines
20 matches
Mail list logo
