Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 99407 invoked from network); 2 Dec 2002 23:12:34 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 2 Dec 2002 23:12:34 -0000 Received: (qmail 10760 invoked by uid 97); 2 Dec 2002 23:13:42 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 10742 invoked by uid 97); 2 Dec 2002 23:13:42 -0000 Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Help: List-Post: List-Id: "Jakarta Commons Developers List" Reply-To: "Jakarta Commons Developers List" Delivered-To: mailing list commons-dev@jakarta.apache.org Received: (qmail 10728 invoked by uid 98); 2 Dec 2002 23:13:41 -0000 X-Antivirus: nagoya (v4218 created Aug 14 2002) MIME-Version: 1.0 Importance: Normal Sensitivity: To: commons-dev@jakarta.apache.org Subject: Quick question/comment re JXPath X-Mailer: Lotus Notes Release 6.0 September 26, 2002 From: Joseph Kesselman Message-ID: Date: Mon, 2 Dec 2002 18:12:28 -0500 X-MIMETrack: Serialize by Router on D01ML243/01/M/IBM(Release 6.0 [IBM]|November 8, 2002) at 12/02/2002 18:12:31, Serialize complete at 12/02/2002 18:12:31 Content-Type: text/plain; charset="US-ASCII" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Question: Apologies if this is on the website, but I didn't see it if so... Is there a good summary of how the XPath axes are mapped in JXPath? Specifically: a) I know bean property equals child, but... is there a concept of Parent? Ancestor? Sibling? Or did you just declare that you're supporting only a subset of XPath without those axes? b) You've got an example which uses //. Given that bean relationships may be arbitrary graphs rather than directed trees, how does JXPath prevent that from potentially becoming an infinite recursion? (a.getB().getC().getA().getB().getC()....) Comment: Something odd is happening to styling of the JXPath pages; half the time, they're displaying with a dark blue background; some of the lettering shows up as white and some as black, with links in blue. The result is pretty near unreadable. The OTHER half the time, they show up with standard black-text-on-white-background. I haven't been able to find a reliable pattern, though entering the URI directly appears to be more likely to cause trouble than following a link from another page. Admittedly, I'm viewing the pages with Netscape 4.75, which probably doesn't have the most robust CSS engine in the world... but I haven't seen this effect before; you may want to look at the generated HTML and see if you can figure out what's provoking it. ______________________________________ Joe Kesselman / IBM Research -- To unsubscribe, e-mail: For additional commands, e-mail: