just look at that url for a second... (if it doesn't go off screen, that is)
the domain... sure. whatever.
viewvc. yeah. k.
webservices/xmlrpc/trunk/server/src/main/java -- damn... we haven't even hit code yet!
org/apache/xmlrpc/server -- WE STILL haven't hit code yet!?!
and then... the kicker:
RequestProcessorFactoryFactory.java
wtf? ... wow. check it:
public interface RequestProcessorFactoryFactory { ... }
this thing declares an interface for a factory that produces other factories that produce things that process requests. processing requests... request processing. factory of factory of... I feel like the lawyer in Idiocracy. duuuh... errr. ummm.
How many freakin' levels of indirection does this world need? It's not even a class.
kill. me. now.
webservices/xmlrpc/ = project organization in a single repo...so it's an SVN artifact stemming from Apache projects being hosted in a single SVN repo.
trunk/ = SVN artifact
server/ = sub project under xmlrpc, I presume, but still another project organization artifact.
src/main/java/ = Maven hell...I understand the reasons for splitting up src into separate areas/languages, but it's still pretty painful to deal with.
org/apache/xmlrpc/server/ = Java package...so really only four elements actually related to Java class packaging here. But of course Java's forcing you to make the dir structure match package structure is irritating...akin to Python forcing your indentation to match the semantic structure of your code.
So I guess there's a few lessons:
Don't use SVN, or at least structure it sanely and consider splitting up repos rather than endlessly nesting.
Don't use Maven.
Don't use Java (because of package naming)? Perhaps, but I've seen some large Ruby projects nest stuff just as deep...so perhaps the lesson would be to break things into smaller projects.
At any rate, the FactoryFactory is pretty well inexcusable...and being an interface, there's some code somewhere acting as a FactoryFactoryFactory.