Java-Frameworks.com is no more

Posted by ryan
at 9:40 AM on Tuesday, September 20, 2005



My little frameworks experiment is coming to an end… Java-Frameworks.com started out as my little personal repository of java utilities, frameworks and libraries that was open to anybody (think a lightweight version of sourceforge with project dependency linking). Rather than keep it around knowing I’m not going to add any functionality or fix any bugs I’ve decided to take it off the air. I have backups of all the projects, so let me know if you need something off of there and I’ll see what I can do.

Here is a listing of all of my little projects that were hosted there (most are several years old and have better alternatives, but for posterity sake….):

  • JDBC Execution Framework v1.1.4: “This is a flexible framework that will remedy the repetition of interacting with a JDBC compliant database. Note: The original form of the framework is outlined in this JavaWorld article. It has since been modified for more flexible use.” [depends on Common Utilities v1.2]
  • Spring Web MVC Chain Extension v1.0.1: see here for summary.
  • Directory Watcher v1.1: “This is a set of utility classes that will monitor a specified directory for any changes to that directory (i.e. additions, deletions or modifications). The monitor will listen to the directory, pinging it for changes on a developer specified time interval. The monitor can accept generic resource listeners, which will be notified when an event occurs on the directory.” [depends on Common Utilities v1.2]
  • Web App Flow Framework v1.1.1: “This is a framework designed to take the repetition out of servlet based application programming. This framework forms an application into a series of request handlers. The flow of each request can then be configured in an XML file that specified which handlers will be called on which requests. The idea is to have several handlers that perform logical independent tasks. By stringing a series of independent handlers together, different chains of reusable functionality can be achieved.” [depends on Common Utilities v1.2 and dom4J]
  • Web App Security Framework v1.0.2: “This framework is designed to provide a way to specify reource level security for a web application. Resources may include jsp pages as well as individual classes. The security of each resource is specified external to that resource, thus seperating the security from the business logic.” [depends on Common Utilities v1.2 and dom4J]
  • Cache Framework v1.0: “This caching framework allows you to build a simple, type-independant caching mechanism with developer specified key types.” [depends on Common Utilities v1.2 and Log4J]
  • Pool Framework v1.0: “This is a framework that will allow for type independent pools to be built very quickly. The common functionality of pooling mechansims has been factored out into a set of clean interfaces and abstract classes. All a developer of a pool needs to code is the factory methods for creating a new poolable item.” [depends on Common Utilities v1.2 and Log4J]
  • Common Utilities v1.2: “Simple utility classes such as NestedException and others…”

It’s funny to look back on work I’ve done in the past and see how different things are now a days. Who writes their own web MVC framework now? JDBC … what’s that?

Comments

Leave a response