On Fri, Nov 07, 2003 at 10:18:59PM -0000, Stephen Colebourne wrote: >... > Core/JavaCore (aka J2SE)
As mentioned elsewhere, the notion of "core" is a bit tough. Maybe tools, or utilities, or ??? > ---------------------------- > - Each has a mission to fill key gaps in the J2SE. > - Minimal dependencies. > [lang] - extensions to the Java lang API > [collections] - extensions to the Java collections API > [primitives] - extensions to cover primitive collections > [io] - (sandbox) extensions to the Java io API > [reflect] - (sandbox) extensions to the Java reflect API Seems like some of the stuff from your Other category would fit in here. Like [classpath], [cli], [configuration], and [resources]. > Objects and Navigation > ------------------------- > - Basic management of Objects and navigating around them > [pool] - object pooling > [beanutils] - introspection and navigation of JavaBeans > [el] - navigation of JavaBeans in line with JSP spec > [jexl] - navigation of JavaBeans > [jxpath] - navigation of XML and JavaBean structures > > Networking > ------------ > - all things http/html/ftp/network Not html. > [fileupload] - support for fileupload > [net] - support for various networking protocols > [httpclient] - an http client Outside of the 'html' comment, I agree with this. > > XML > ------ > - all things xml > [betwixt] - JavaBean to XML conversion > [digester] - high level XML parsing assistant XML would be fine, but should we consider this as "markup" and put any HTML-related code here, too? > > Enterprise (aka J2EE) > ---------------------- > - strictly server side > [daemon] - server daemon > [modeler] - J2EE JMX spec helper > [messenger] - (sandbox) J2EE JMS spec helper Should this be part of Commons, or part of Geronimo? If the codebases are going to move, should that move towards Geronimo instead? > Database > --------- > - all things db > [dbcp] - database pooling > [sql] - (sandbox) unified sql Good. > Other > ------ > [cli] - command line handling > [logging] - log wrapper > [discovery] - handling Java's classpath > [attributes] - (sandbox) C# attributes in Java > [cache] - (sandbox) general object cache > [chain] - (sandbox) chain of responsiblity pattern > [configuration] - (sandbox) helper for config > [functor] - (sandbox) library encouraging small functors > [resources] - (sandbox) helper for i18n config > [threadpool] - (sandbox) pool for threads > [vfs] - (sandbox) virtual filing system I don't think we want an "other" category. Thus, if we can sort these out to other buckets, that would be great. See my thinking above for some of these. > Standalone (New TLP) > ----------------------- > Should be, but has a community problem. > [jelly] - XML scripting language Is this really "commons"? How is this a reusable component? Should it move out of jakarta-commons to a jakarta project? Is it really "big enough" to be a TLP? > Should be, but has licencing problems ATM. > [hivemind] - application framework I imagine those will get cleared up. Just needs to happen. Given that, does this come to A-C, or migrate up to Jakarta? I saw the bit about migrating from the sandbox to J-C, but how is an "app framework" actually a "commons-style component"? > Maybe, although fairly new > [math] - maths component This would probably fall into your basic support category. "core" > --- > (Note that the sandbox components are not all listed - I've excluded some > without websites, and those that appear to be dead. Should really xref > Henri's sandbox doc) > > These categories also reflect to some degree the personalities involved. To > that end, potentially XML, DB and Enterprise could be merged to form a > stronger group, with [discovery] and [logging] too. Should be topical rather than person-based. > For oro/rexexp, there could potentially be a 'Text'/'String' group. Well, if we have a "text" group, then XML and HTML could go there, too. Cheers, -g -- Greg Stein, http://www.lyra.org/
