I think you actually have to narrow your criteria. Within jakarta commons we try to focus on one component approach versus multiple component approach, even though that doesn't always happen. And, in many ways, jakarta commons has been VERY sucessful in providing reusable components. Just look at the list of dependees in Gump for typical components. Or the number of other OSS sites that say "These are my util classes, but you might as well use commons-lang or commons- something else".
At a bigger level, everybody has different ways and thoughts on how to set things up. That is why projects like Spring or Keel exist. They attempt to provide the glue *between* all the other approaches. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
