Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Received-SPF: pass (hermes.apache.org: domain of schulz@sce.carleton.ca
 designates 134.117.56.4 as permitted sender)
Message-ID: <20050615235156.u9cl6xtz8kswgko4@webmail.sce.carleton.ca>
Date: Wed, 15 Jun 2005 23:51:56 -0400
From: schulz@sce.carleton.ca
To: Jakarta Commons Developers List <commons-dev@jakarta.apache.org>
Subject: Re: jxpath ?
References: <20050615170153.65517.qmail@web26601.mail.ukl.yahoo.com>
In-Reply-To: <20050615170153.65517.qmail@web26601.mail.ukl.yahoo.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset=ISO-8859-1;
	format="flowed"
Content-Disposition: inline
Content-Transfer-Encoding: 7bit
User-Agent: Internet Messaging Program (IMP) H3 (4.0.3)

Hi Dimitri,
hi Ricardo,

I asked some week ago about JXPath and adaption to Java5, which seems to
have gotten lost. Would it make sense to also find out, if there could
be nice impacts on such an adaption? I am new to commons, so I do not
know how things work, but maybe I can support, too.
Currently, I am using JXPath as access context for DOM objects realizing
a serializable state for application objects.

Cheers,
Stefan

Ricardo wrote:
> Hi Dimitri,
>
> Glad to see you're "alive"...
>


---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org