Return-Path: Delivered-To: apmail-commons-user-archive@www.apache.org Received: (qmail 63597 invoked from network); 8 Feb 2009 23:13:03 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 8 Feb 2009 23:13:03 -0000 Received: (qmail 65298 invoked by uid 500); 8 Feb 2009 23:12:59 -0000 Delivered-To: apmail-commons-user-archive@commons.apache.org Received: (qmail 65243 invoked by uid 500); 8 Feb 2009 23:12:59 -0000 Mailing-List: contact user-help@commons.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Commons Users List" Delivered-To: mailing list user@commons.apache.org Received: (qmail 65232 invoked by uid 99); 8 Feb 2009 23:12:59 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Feb 2009 15:12:59 -0800 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of ahhughes@gmail.com designates 209.85.142.190 as permitted sender) Received: from [209.85.142.190] (HELO ti-out-0910.google.com) (209.85.142.190) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 08 Feb 2009 23:12:53 +0000 Received: by ti-out-0910.google.com with SMTP id j3so1397498tid.10 for ; Sun, 08 Feb 2009 15:12:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=hiF0CdkPKj7iJs4eNaQi9k3sG+xnRj8t6Y0nYj2mr1g=; b=ZM3FWuiD6fdzkHzd71YPmmHLhXmPjzF3D6Oofs/nGK7Gw1KWiEWr40DnndJ+DmY4XN HnQYq0GizK69Uk0Op3NwoG3yLPfgsnTF5ouPcwEGFzjk/nFJkbG0UYmaVHXVQJkBJbzg Q9FSVqdARhgMY6uBBf5xsPWwps11IqkqR4dFg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=wVuhxv/ECcHGwhXK71nF9U83JZwLmT6i2uEFBvGEIFYsQLJyN7GAY8lBWeaADHhNCs GruVlRHBkeaqrGAoeFqJePAGNE2KR3qHupZr/kqrcGlUolvnrXh0miJ5UuQGtr6IbE+Z jiP2PeGcoSDVzrn1yuGWmKILNHrrkvMCvpYqs= MIME-Version: 1.0 Received: by 10.110.95.11 with SMTP id s11mr2547983tib.24.1234134751588; Sun, 08 Feb 2009 15:12:31 -0800 (PST) In-Reply-To: <462514.30207.qm@web55103.mail.re4.yahoo.com> References: <3ee326610902021420k35d3eb18vfa357e3ea09ddef0@mail.gmail.com> <462514.30207.qm@web55103.mail.re4.yahoo.com> Date: Mon, 9 Feb 2009 09:42:31 +1030 Message-ID: <5f528cf40902081512md5d5853n577b8516c66e17b6@mail.gmail.com> Subject: Re: JXPath - is JXPath dead in the water? From: Andrew Hughes To: Commons Users List Content-Type: multipart/alternative; boundary=0016e64e9300792fe40462706390 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64e9300792fe40462706390 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Hi Matt + Others, Thanks for your replies! I've taken your advice and re-seeded my question on a brand new thread with subject "JXPath over Generic Collection, How?". If anyone can help with this I would be MOST appreciative. Also, I am happy to contribute back to the project with examples if I can get some svn access. Big thanks, and hopefully you can please read my other post (fingers crossed). Andrew. On Tue, Feb 3, 2009 at 9:24 AM, Matt Benson wrote: > > --- Adrian Mitev wrote: > > > On Mon, Feb 2, 2009 at 5:10 PM, Matt Benson > > wrote: > > > > > > --- Andrew Hughes wrote: > > > > > >> Hi All, > > >> Is JXPath dead in the water? I can't find a post > > >> here in 2009 and very > > >> limited posts in 2008. > > > > > > Hi Andrew, > > > JXPath is considered to be in "maintenance mode." > > > In general, this means that this component is > > > considered to be more or less "complete" and that > > for > > > the most part, changes to the code will target > > bugs. > > > Specifically with regard to JXPath, any new > > features > > > considered would address shortcomings with support > > for > > > the XPath 1.0 specification. If you encounter > > issues > > > with JXPath feel free to post your questions to > > this > > > list; if you don't get an answer the first time > > just > > > keep pushing! ;) > > > > > > HTH, > > > Matt > > > > Will XPath2 be supported in the near future? > > Originally that was under consideration, but to be > honest everything I personally know about XPath (1.0) > I learned in the course of supporting JXPath, so as > JXPath's primary maintainer I presently don't consider > myself capable of making such an upgrade. There is an > open JIRA issue for XPath 2.0 support: > http://issues.apache.org/jira/browse/JXPATH-67; > further if you or anyone else has ideas on this feel > free to start a discussion thread on > dev@commons.apache.org (the real convention on these > mailing lists is to preface your subject with the > component ID e.g. "[jxpath] XPath 2 support"). A nice > start might be a boiled-down list of the basic > differences between versions 1 and 2. > > -Matt > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: > > user-unsubscribe@commons.apache.org > > For additional commands, e-mail: > > user-help@commons.apache.org > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: user-unsubscribe@commons.apache.org > For additional commands, e-mail: user-help@commons.apache.org > > --0016e64e9300792fe40462706390--