Thanks for the reply Daniel,
My StringW class has a a handful of classes that it exclusively uses, and
a handful of other W classes which it uses some methods in. (W for
Wrapper, ie) a class that provides static methods for acting on a
particular java class).
What's your view on this? Should I push all these classes up? just inline
the code? Ignore methods that have sizeable external dependencies?
Bay
On 22 Aug 2001, Daniel Rall wrote:
> [EMAIL PROTECTED] writes:
>
> > I'm in the process of cvs commiting a String taglib to the Jakarta Taglib
> > project. It's a fairly simple concept sitting on top of a StringW utility
> > class.
> >
> > I saw some conversation on the Velocity project mail list about
> > StringUtils in their projects and sent an email asking if a common String
> > lib shoudl be defined. Then I noticed an emailer with the commons project
> > in their sig and realised that there already is a place for such a thing
> > :)
> >
> > So I'd like to either submit my code, discuss how to create such a thing,
> > or get told that it's not needed. Here's the javadoc:
> >
> >
> >
>http://www.generationjava.com/java/string/docs/org/apache/taglibs/string/util/StringW.html
>
> Hi Bay. Send me a patch for jakarta-commons-sandbox/util's
> StringUtils class, or commit the changes yourself.
>
> Daniel Rall
>
