On Tuesday 17 September 2002 06:23 pm, Stephen Colebourne wrote: > I have just promoted the ToStringBuilder to the commons proper builder > package. It comes with an associated ToStringStyle class that allows most > toString styles to be designed. 4 common styles are pre-defined. In > addition a StandardToStringStyle allows easy customisation of the style as > a JavaBean. > > Interested parties should check it out. > > I believe that this now concludes the builder subpackage and tests. Its now > up to the release manager (who was that?) to decide on whether they're > allowed into the release or not.
No one had volunteered yet. BTW, I saw the commits re static. Good idea. The only way I can see statics coming into play is if there are threading issues. And the builder classes are inherently thread UNsafe. Particularly equals and compareTo, as both objects would need to be locked. Even hashCode, if the object were accessed by another thread, could produce indeterminate results. Of course in any situation where that happens, you're probably fubared anyway. Mutable value types are dangerous. Post release, there should also be a discussion of introspectionX versions of the reflectionX methods. I know we ruled it out of scope for [lang], since it's more of a bean thing. But the builder classes aren't things that [beanutils] is really doing, at least at the moment. And duplicating the XBuilder classes in [beanutils] doesn't really seem to me to be a good way of serving our clients. [Read this as, I've got a really dandy use of ToStringBuilder in mind, except that the classes I've got to work with don't have fields, just getter/setters. Database row objects, generated by Oracle's jpub.] -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
