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 Mon, 08 Mar 2004 19:13:10 GMT
Yes, I think Jestr could be incorporated cleanly into the ToStringBuilder hierarchy, either
as a subclass of ToStringBuilder, or as a subclass of ReflectionToStringBuilder.  

I would be happy to incorporate it into org.apache.commons.lang.builder, but there's just
something about this categorization that bugs me a little:  Isn't the term "builder" a bit
misleading here?  After all, Jestr doesn't really care if I am building a toString() method
or not, and if I am stringifying some legacy or third party class, then what exactly am I

---------- Original Message ----------------------------------
From: "Gary Gregory" <>
Reply-To: "Jakarta Commons Developers List" <>
Date:  Mon, 8 Mar 2004 13:43:51 -0500

>> However I think Jestr is a
>> little different from the ToStringBuilder stuff because it isn't
>> necessarily concerned with helping you implement toString() methods;
>> instead, it's more concerned with helping you log *arbitrary* objects,
>> even if you don't have access to their source code to change their
>> toString() methods.
>Note that the o.a.c.l.builder package also provides the ability to
>operate on an arbitrary object. Please see: 
>(1) The class ReflectionToStringBuilder: 
>(2) The ToStringBuilder methods which forward to
>To unsubscribe, e-mail:
>For additional commands, e-mail:

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

View raw message