Return-Path: Delivered-To: apmail-jakarta-commons-dev-archive@apache.org Received: (qmail 69803 invoked from network); 18 Jul 2002 23:24:35 -0000 Received: from unknown (HELO nagoya.betaversion.org) (192.18.49.131) by daedalus.apache.org with SMTP; 18 Jul 2002 23:24:35 -0000 Received: (qmail 25437 invoked by uid 97); 18 Jul 2002 23:24:54 -0000 Delivered-To: qmlist-jakarta-archive-commons-dev@jakarta.apache.org Received: (qmail 25415 invoked by uid 97); 18 Jul 2002 23:24:53 -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 25397 invoked by uid 98); 18 Jul 2002 23:24:53 -0000 X-Antivirus: nagoya (v4198 created Apr 24 2002) Date: Fri, 19 Jul 2002 09:24:33 +1000 From: Jeff Turner To: Jakarta Commons Developers List Subject: Re: [latka][jelly] commons-vfs? Message-ID: <20020719092433.C9889@snow.socialchange.net.au> Mail-Followup-To: Jakarta Commons Developers List Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N Thanks for setting up the build James, On Wed, Jul 17, 2002 at 03:52:33PM +0100, James Strachan wrote: ... > OK so now we've got the first cut of VFS as a commons component, how would > you see this working inside Ant/Jelly/Latka/Anteater? > > The way the iteration works in Jelly is to define a then iterate > over it. e.g. > > > > > > > > > > > > > Found ${file.absolutePath} > > > > > > So maybe we need some way to define a VFS fileSet and work in a similar way? That was the general idea. Then there can be Latka tags inside the , operating on each 'file'. It would require quite a lot of coding to get to this stage though. The HTTP->VFS layer is not trivial (unless it's Cocoon you're testing:), and Latka/Anteater would need some recoding to use the VFS API. > Then we can iterate over the set, do set unions, manipulations etc. > The XPath-like language you mention, I guess we could use that to > define include/exclude patterns as an alternative to the Ant ones. I was imagining stuff like: or if the VFS back-end supported federation[1], then we could look inside nodes, eg "WEB-INF/web.xml/web-app/servlet/*", or "/index.html/*" for "All files linked to from index.html". (incidentally and totally OT, wouldn't it be cool if there were XPath-enabled shells.. eg 'ls //*.txt' for "all .txt files", or 'ls *.txt[@content='*foo*']' for "txt files containing 'foo'") Ant currently has Selectors[2], which let one limit a fileset based on things like file date, size, etc. I hope Ant2 will have pluggable expression languages, which would provide a more compact way of using selectors. All just wild imaginings of how to factor out as much as possible between functional testing tools. --Jeff [1] http://java.sun.com/products/jndi/tutorial/beyond/fed/ [2] http://jakarta.apache.org/ant/manual/CoreTypes/selectors.html > Thoughts? > > James -- To unsubscribe, e-mail: For additional commands, e-mail: