Re: [dom4j-user] incompatibility with 1.4 (1.5b1?)

[Maarten Coene]

This is a bug, your xpath expression should return an attribute. 
However, I was unable to reproduce your problem (I tried it with the 
current CVS version of dom4j and with 1.5 beta1).

Could you provide your classpath? Maybe there is a problem in there... 
And just to be sure if your example below is correct: is the "summery" 
node the same as the "n" node (the one returned by the selectSingleNode 
method)?

Maarten
[EMAIL PROTECTED] wrote:
Hi!
Previously 

	Node n = doc.selectSingleNode( "/HTML/HEAD/[EMAIL PROTECTED] eq 
'description']/@content" );

actually returned the Attribute "content" of META. Now actually META is 
returned and a 

        Element e = (Element)summary;
        System.out.println(e.attribute("content").getText());
is required. Is this a bug or was this a bug?
Timo
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user
 


-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 - 
digital self defense, top technical experts, no vendor pitches, 
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
dom4j-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dom4j-user