commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "David Gilliland" <>
Subject RE: Proposal for the Commons Sandbox
Date Tue, 09 Mar 2004 18:32:59 GMT
>What's in IO/Collections that you can't do without for Jestr?
Looking at it again, I'm not using those as much as I had thought.  In Collections I make
one use of DualHashBidiMap, a few uses of IteratorChain, and in IO I use NullOutputStream.
 I do use Logging quite heavily though.  

But going forward I'd like to incorporate the JXPath stuff for predicates.  I think it would
be highly cool to be able to give an XPath expression and say "for all nodes in my object
graph that match this expression, I want such-and-such stringification style".  To reference
JXPath from Lang would obviously not be acceptable.

---------- Original Message ----------------------------------
From: "Shapira, Yoav" <>
Reply-To: "Jakarta Commons Developers List" <>
Date:  Tue, 9 Mar 2004 08:43:07 -0500

>>However, this approach would introduce some dependencies on non-Lang
>>components (IO, Collections, etc) into Lang (the Functor dependency is
>>quite trivial and easily removed, but the others are used heavily).  I
>>don't know if this is an issue or not.
>It's definitely an issue: AFAIK we don't want lang to depend on those.
>What's in IO/Collections that you can't do without for Jestr?
>>Also, there is the dependency on the properties file for configuration,
>>which is an unfortunate hack that I hope to replace with Commons
>>Configuration.  Thus there would be a dependency from Lang to
>>Configuration.  Again, I don't know if that's an issue or not.  Is
>>any precedent for a Configuration dependency of this sort?
>There's no precedence for a Configuration dependency of any sort since
>there's never been a Configuration release.  And if we keep adding
>features prior to the 1.0 RC, there won't be a Configuration release for
>a while probably ;)  (I'm not saying that as a bad thing, just a matter
>of fact).
>Yoav Shapira
>This e-mail, including any attachments, is a confidential business communication, and
may contain information that is confidential, proprietary and/or privileged.  This e-mail
is intended only for the individual(s) to whom it is addressed, and may not be saved, copied,
printed, disclosed or used by anyone else.  If you are not the(an) intended recipient, please
immediately delete this e-mail from your computer system and notify the sender.  Thank you.
>To unsubscribe, e-mail:
>For additional commands, e-mail:

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message